Companies interested in test automation, do'nt ask: “should we invest in test automation?” but rather “How much Test Automation we need?”; “In which places can we build our test automation?” and other operational and implementation aspects.
The reason is that in today’s world of fast release cycle that our customers demand of us - when building complex products - we are obliged to do test automation, and run fast testing/checking.
Industry speaks of 15-20% code change in a new release (already in production). That means we have a potential of 80-85% regression – that is a lot of testing to be done, in a short while, if we want to cover most of it (even if at least the high risk parts). That regression high coverage can be acheived with high % using smart test automation.
Burning questions any company ask itself
When approaching a test automation implementation, one needs to consider many 'burning' questions, which will affect the ROI:
- Would that fit our multiple technology environment?
- Would that stand low maintenance when our product change?
- Would that be modular enough to enable flexibility of creating new tests or change existing ones?
- Would that enable us to reuse automated test scenarios already built?
- Would that fit testers and developers and other stakeholders to run?
- How would that leverage our ability to run a lot of regression test coverage?
- Will we be able to create test automation to our new functionality (not just regression)?
- Would that fit our mobile/cloud/other technology product platform?
- Which tools should we use and how they can be integrated with the existing tools we have?
- When can we expect return on investment from the developed platform?
Answering these questions (and more), and building/implementing such a test automation platform/framework that will give the right solution, is what we do at QualityWize.
How will QualityWize support you?
We will first, discuss and support you in finding out how test automation can leverage your testing, and contribute to your benefits (or ROI in test).
We will than, typically, evaluate the needs for test automation, the environment the project is in (technology, skills, operation, process, etc.), perform a pilot or proof of concept if necessary, and suggest a way forward – either building a test automation platform/framework, or altering an already existing one.
We will support tool pilot and evaluation – where necessary. Support the process for implementation of tools, integration, integration into the existing lifecycle, and coaching the necessary skills for successful implementation.
We will then support the creation of your automation test cases and scripts, and may offer you low cost solution as well, with our Off-shore partners operations.