CA’s Agile Requirements Designer & Perfecto’s CQ Lab: A Match Made in Heaven
With the rapid pace of technology growth today, it’s no surprise that organizations are under constant pressure to deliver working software faster than ever before. But at what cost? What were once well thought out test cases are now giving way to loose requirements and software that is riddled with bugs.
This is where CA's Agile Requirements Designer (ARD) is helping companies make exponential progress by providing a tool for end-to-end requirements gathering, which then automatically creates the full gamut of automated test cases necessary for a quality product.
By itself, this is a great tool for generating test cases, but there is a limit to the amount of automation that can be created using standalone, open-sourced frameworks. However, leveraging this tool in combination with Perfecto’s CQ Lab and Quantum framework turns ARD into a powerhouse, enabling automation of 90% (or more!) of test cases with the click of a button… all while using a common Web Driver-based framework.
Essentially, teams are able to create a fully automated suite of end-to-end tests directly from the requirements. And what makes this even better, is that code can be reused at all the different stages of the SDLC, enabling organizations to deliver higher quality software to market earlier, and at less cost!
Let’s dive in. I’ll walk you through the simple setup, integration, and workflow so that you can start benefiting immediately.
Project Quantum Setup
To start, download the Project Quantum framework from GitHub.
There are a few basic setup steps that will need to be completed within this framework. Detailed instructions are in the ReadMe file and can be found here.
Agile Requirements Designer Setup
Then, you will need to download the cucumber.config file found here.
Next, to import this file into Agile Requirements Designer, click the ‘Automation’ icon, and import the cucumber.config as shown.
Now, create the workflow diagram for your application. For each block, there should be a cucumber automation step associated.
And in order for the cucumber script to be output as expected, you will need to enter that text in the ‘Process Details’ tab under ‘Data Notes.’ You can also add dynamic test data as needed.
Once the flow chart is completed, we are ready to generate the test cases and automation. From the ‘Manage’ tab, click ‘Path Explorer.’ Now click the Play button to start optimization. Once complete, you will want to click to store all test cases.
Next, click on the tab to ‘View Test Cases’, and then click to ‘Export Automation Scripts.’
At this point, all of your test cases are generated and can be viewed. But before you export them to run, there are a few housekeeping items you will want to take care of. To start, click the ‘Merged Scripts’ button. Then, change the file name to end in ‘.feature’. Next, add a Header Parameter as shown. This will provide a feature tag that allows a simple way to execute the script. Finally, save the script to the ‘src/main/resources/scenarios’ folder of the Quantum framework. Then click ‘Export.’
Once complete, these tests can be kicked off via the tag in the Quantum project, using Maven or TestNG commands.
And that’s all there is to it! Now you can add this into your existing CI pipelines across Dev, Test, and Ops for an even better result.
Best of luck!