To quote directly from the FX Kickstart for Testers paper;
As a competent test professional you’ll know that fundamentally you can test in any domain. That domain could be travel, healthcare, engineering, retail, etc. and of course finance. Ultimately we can say with sincerity, it’s all software testing and the skills and knowledge of our profession that we possess, apply no matter what the domain.
However, there are two very real caveats with this perspective that will limit our effectiveness in a given domain until overcome:
- We will initially lack understanding of the testing challenges in the domain, thereby limiting our application of contextually relevant testing techniques and approaches
Once we address these caveats we will understand the unique testing needs of the domain in a contextually relevant way and be able to communicate with our colleagues effectively.
- The domain will have unique vocabulary and concepts that must be understood if we are to translate its meaning and communicate effectively
- The nature of the problem is known
- What problems are being caused to current business operations, what limitations it is causing
- What is limiting the client from solving the problem themselves
- What attempts have been made to solve the problem and what the outcome was
- Timescales for the problem needing solving and why, is anything dependent on the test work
- What kind of environment the client has in place culturally; open, communicative, blaming
- How they work technically; adaptive / descriptive, predictive / prescriptive, hybrid
- If they are subject to professional or legal compliance and auditing
- Any issues with public perception or on a branch / regional basis