How Test Automation Can Get You Closer to Achieving Agile Testing

by October 6, 2017

You can’t do Agile Testing without Test Automation

It’s hard to believe that after 30 years, 70% of testing is still manual today. A major bottleneck in the SDLC, legacy testing remains a barrier to speed and quality – unable to keep up with today’s agile, continuous testing model. But as more organizations adopt test-driven, agile development methods, they gravitate towards test automation – enabling test teams to automatically generate reusable test assets like test cases, test data, and test automation scripts right from requirements.

Applying Model-based Testing approaches for more effective test automation

Model-based testing (MBT) helps you avoid costly defects, stemming from poor requirements. It enables you to automate testing activities, shortening testing time dramatically. And so, your high-quality apps are delivered faster at lower costs.

MBT increases the likelihood that software will deliver more accurately, satisfying desired outcomes as it provides a set requirements that are both unambiguous, and complete. This reduces the total number of feedback loops needed before software delivers on the business requirements, reducing frustrating rework and delays. This ability to continuously develop solutions in an effort to maximize their value to customers is further facilitated by the ability to quickly and easily respond to change.

The question then becomes, in what ways does MBT drive test automation effectiveness?

Engineer and design better Requirements

Start with modeling requirements as an active flowchart, versus writing them in inefficient text-based methods. With 64% of defects coming from poorly-defined requirements, modeling using a flowchart eliminates unclear requirements – while boosting collaboration and communication.

With visual modeling approaches to Requirements Engineering, you can create models that represent the behavior of your application and the requirements associated with that behavior. With these models as “flows”, you can then see the logical paths through the application and create test cases for those paths. As a result you can automatically generate optimal test cases and test automation scripts – right from your requirements. And that means no more endless iterations with developers and testers to clarify ambiguous requirements.

Optimize Test Cases

Next, generate optimized sets of test cases automatically. This means creating test cases right from the flowchart as user stories are created, and testing the functionality at maximum coverage with the smallest set of tests.

With the right tool, you can collect all test cases into a single venue and display them as a test plan. These test cases are automatically extracted from the complete set of requirements from the visual flows. Applying filters, only the paths or test cases that meet the filter criteria are displayed – so you end up with just the right set of test cases that meet your desired test coverage.

Automate Test Design Processes

With the ability to do automated testing, you can free yourself up from manually writing and maintaining your tests, enabling you automatically create test cases and generate test automation scripts, right from your requirements.

As a tester, you record automated tests and export script files that you execute with your test automation framework. Instead of having to manually refactor and record all test variants, you can use tools like CA Agile Requirements Designer to automate test script generation for your test paths. Automating testing on various platforms such as mobile, desktop, web, client/server, or mainframe, tools like CA Agile Requirements Designer generate your test automation scripts for the test engine of your choice such as eggPlant, HP UFT, Ranorex, Selenium, and Cucumber/Gherkin and more. Click on this video link below to see an example of how Test Automation works in this particular use case.

Test Automation

Finally, finding and fixing test scripts that fail whenever your requirements change doesn’t have to take long as this becomes automated just the same as part of automating the ‘change in requirements process’. This cuts the time wasted on manually finding and fixing tests when requirements change, because as changes occur they automatically initiate impact analyses and create or repair tests to maintain test coverage – while building up a library of reusable test assets that can be run or rerun as test automation artifacts.

CA offers comprehensive solutions that automates the most difficult testing activities – from requirements engineering through test design automation and optimization. Start your Free Trial of CA Agile Requirements Designer today and fast track your testing at the speed of agile.