The Importance of Volume in Automated Software Testing

All too often, software development organizations look at automating software testing as a means of executing existing test cases faster. Very frequently there is no strategic or methodological underpinning to such an effort. The approach is one of running test cases faster is better, which will help to deliver software faster.

Even in organizations that start to build a test automation effort on a good foundation of strategy, methodology, and supporting tools, taking such a narrow view of the test automation effort misses a huge dynamic.

Simply running existing test cases faster reduces testing time but does not increase testing capacity. Less time is taken to test, a good thing, but software testing may still be falling woefully behind software development and still represent a huge bottleneck. This is further exacerbated by the rapid increases in productivity that software development has undergone and continues to enjoy.

This approach can also lead to another detrimental dynamic. From this approach, often times organizations look to hand the test automation off to inexpensive low-skill organizations that have relatively little experience with testing and test automation – often times offshore. While this can work given the relatively modest goals for automation it creates a future problem. At some point in time the organization is going to come to realize that they need to substantially increase the volume of testing in order to keep pace with development, and they will have entirely the wrong team in place to accomplish this.

More than Automation, the Goal Should be High Volume Automation

To be truly successful in test automation requires a change in emphasis. While it is commendable to do the existing testing faster, the goal must be to do a very high volume of test automation. This will allow software testing to truly keep pace with development. By setting this as a goal, and putting in place the necessary processes, organization, and partners, a software testing organization can keep pace with development and make valuable contributions to software quality.

The Keys to High Volume Testing and Test Automation

What, then, are the keys to success in high-volume test automation? There are many key ingredients, including:

  • An overall software testing strategy that informs methodology and tool selection.
  • A methodology that supports the strategy and makes it easy to design and implement tests. As important, the methodology must also make it easy to maintain automated test cases. An organization does not want to trade the bottleneck of manual testing with a new bottleneck – maintaining test cases. Easy to maintain and reuse test cases are critically important to obtaining high levels of test automation and testing.
  • Software testing tools that support the strategy and methodology and make it easy to design, implement, maintain, and reuse test cases.

Another factor that can be critical to the success of such an effort is engaging the right partner to facilitate the process. Organizations that feel they are weak in the strategy and process department when it comes to software testing should look to a partner who can help them to align quality assurance objectives with business objectives. Such an organization can help to:

  • Define and refine objectives
  • Align objectives and business vision
  • Maximize test efficiencies with the latest methodologies and tools

Companies with a handle on strategy and process may wish to engage a partner who understands how to translate the vision into a high-volume testing program; one with experience implementing high-volume methodologies and the tools that support them. Equally as important is a partner with experience employing global resource strategies to help keep costs down.

Benefits of High Volume Testing

There are many benefits to a testing program that sets goals for very high volumes of developed, maintained, and executed test cases. These include:

  • A software testing organization that can keep up with the pace of development
  • Increased testing coverage
  • Improved software quality (assuming that good test cases are designed and automated)

Conclusion

Successful test automation programs do not simply aim to run existing test cases faster. Truly successful automated software testing programs set much more lofty goals. They set the goal of providing truly high volume testing and test automation. They implement the right strategies, methodologies, and tools to support high volume. Doing so, testing can keep pace with development and make big contributions to software quality.

Rob Pirozzi
Over 20 years of sales, marketing, management, and technology experience in high technology with exposure to industries including financial services, healthcare, higher education, government, and manufacturing; demonstrating a strong track record of success.

The Related Post

Introduction A characteristic of data warehouse (DW) development is the frequent release of high-quality data for user feedback and acceptance. At the end of each iteration of DW ETLs (Extract-Transform-Load), data tables are expected to be of sufficient quality for the next ETL phase. This objective requires a unique approach to quality assurance methods and ...
The path to continuous delivery leads through automation Software testing and verification needs a careful and diligent process of impersonating an end user, trying various usages and input scenarios, comparing and asserting expected behaviours. Directly, the words “careful and diligent” invoke the idea of letting a computer program do the job. Automating certain programmable aspects ...
Many organizations rely on HP Quality Center to design test plans and track test results. TestArchitect’s Quality Center integration makes working with QC as easy as pie. TestArchitect (TA) is a three-in-one tool for Test Management, Test Development, and Test Automation. Users can create and manage test assets, execute tests, track and analyze test results, ...
The Cloud demands that we be as nimble as possible, delivering features and fixes in almost real-time fashion. Both customer and provider rely on software development that can maintain quality while being light on its feet and constantly moving. In addition, Cloud-oriented systems tend to be highly complex and dynamic in structure — more than ...
Developers of large data-intensive software often notice an interesting — though not surprising — phenomenon: When usage of an application jumps dramatically, components that have operated for months without trouble suddenly develop previously undetected errors. For example, the application may have been installed on a different OS-hardware-DBMS-networking platform, or newly added customers may have account ...
5 roadblocks in vehicular autonomy that complicate Software Testing Experts in the field have previously referred to air travel as somewhat of a gold standard for autonomous vehicle safety, but after Boeing’s two tragedies, that analogy can no longer be used when talking about self-driving cars. This was after Boeing’s 737 MAX Jets have found ...
For those that are new to test automation, it can look like a daunting task to undertake For those who are new to Automation, it can look like a daunting task to undertake, but it only seems that way. If we unpack it and pinpoint the fundamentals, we can have the formula for the desired ...
September Issue 2018: The Secrets to Better Test Automation  
There are few topics in quality assurance testing that cause as much confusion as smoke testing versus sanity testing. The two names would seem to describe very different practices— and they do! But people still get them confused, since the distinction is somewhat subtle.
Test automation can provide great benefits to the software testing process and improve the quality of the results…. but its use must be justified and its methods effective. The reasons to automate software testing lie in the pitfalls of manual software testing… As we all know too well, the average manual software testing program:
There is no one recipe to make big testing a big success. It takes planning and careful execution of the various aspects, like test design, infrastructure and organization – a mix that can be different for each situation in which you may find yourself. In writing about big testing, the first question that comes up ...
Test execution and utility tools that can make your job easier My first exposure to the necessity for testers to have an array of tools was from the groundbreaking article “Scripts on my Toolbelt” by Danny Faught. Danny laid out the ideal approach to any testing job, and it got me thinking “How can I ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe