How to Crack the Test Design Code with Model-Based Testing

Gedeon Hombrebueno

This edition of Software Confidential is by Gedeon Hombrebueno, Principal Product Marketing Manager at CA Technologies. Gedeon focuses on bringing to market CA’s Continuous Delivery and Testing solutions.

Model Requirements as an Active Flowchart.

Building a model can simplify your requirements-definition process. Modelling requirements as a flowchart eliminates unclear/incomplete requirements. Time-to-learning is minimal because your business analysts are familiar with this format. Bringing users, business analysts and IT into alignment with a model that everyone can share, review and use promotes collaboration and increases efficiencies.

Generate Optimum Sets of Test Cases.

Exceeding your app delivery goal for quality with maximum functional test coverage is possible. Start by generating test cases and scripts automatically, straight from the flowchart, when user stories are created. Then link the right data and expected results to the relevant user stories. Finally, test the functionality at maximum coverage with the minimum set of test cases.

Automate, Automate, Automate.

Using an "automation generator" helps you keep up with changing user requirements. So, as a change to the requirements occurs, it triggers an impact analysis that creates or repairs test cases. Build a library of reusable test components that can be run or rerun as test automation artifacts. Maximizing the value of your existing testing frameworks lets you easily synchronize or export test cases and test scripts.

By Gedeon Hombrebueno | 01 Nov 2017