CA Agile Requirements Designer Valuable Features

Carrie Strickland
QA Group Manager at a financial services firm with 1,001-5,000 employees
* Now, we get automated test cases, where before we did not. It cuts out the construction time of testing, about 75%, is what we found. * It is a store that we keep all of our requirements in where, before projects would come in and we would not have a place where we keep the past requirements so there was always a fight between development, testing, and the business writers because they can't remember how functionality works. Now, there is a black and white copy of how the processes are flowing through the system, so there is not a fight anymore about what is happening and what is not happening. View full review »
Mridul Balaraman
Machine Learning Lead at a engineering company with 10,001+ employees
The basic requirements modeling is its most valuable feature. It was easy to implement the tool, onboard, and train people in the organization. View full review »
Gireesh Subramonian
Assistant Manager Business Analyst at Ernst & Young
In the case of a big epic, we are able to create it. Then, based on backlog creation, we will be able to create the user stories under that particular feature. Also, defects can be traced in the solution. View full review »
Lana Rousakovski
Senior Leader in Software Testing and Process Improvement at a tech company with 10,001+ employees
The ability to create models/diagrams at multiple levels (nest/embed them) helps in taking models from high-level business requirements and building them into detailed requirements models and test models. Plus, it helps reuse lower level models. It also allows maintaining models at appropriate levels, even for very complex systems/solutions. The above features also help to avoid redundancy and use appropriate level models for different levels/phases of testing and/or communicating to different audiences. Integration with TDM, test data management tool, provides the ability to generate data or use identified (preset or parametrized) test data. It allows significant expansion of test coverage and flexibility, without creating new tests and needing to maintain them. Integration with automation is one of the reasons we started to consider moving to this tool from our original tool for implementing test modeling. ARD appears to have better integration with Selenium. It also has the ability to record scripts/flows using Selenium Builder and import them into ARD, which will then create and optimize a model based on that. Measuring test coverage helps in one of the most challenging tasks. It has logic that can help to select the right set of scenarios and know what coverage it will provide. Handling loops in models was one of the challenges that we came across in our previous tool. ARD seems to have better control and logic over handling loops in models. View full review »
FrontLin0598
Front Line Manager at a energy/utilities company with 1,001-5,000 employees
I like the optimization, because it gives me an idea of the minimum number of test cases. It also gives me an idea of coverage. The integrations with other tools is very important for our continuous testing process. View full review »
SeniorITb049
Senior IT Manager at a manufacturing company with 10,001+ employees
The most valuable feature for us is the automatic creation of the test cases, based on the models. And the impact analyzer that shows you where your change is impacting your test cases, and the ability to export that to our TFS Instance. View full review »
Ray Oliver
Director Of QA with 1,001-5,000 employees
* The co-monitorial modeling. It lets us reduce the amount of scripts that we need to execute to get complete coverage. That is really important to us. * Traceability from requirements through test cases. View full review »
Shubham Jain
Test Engineer Senior Analyst at a tech services company with 10,001+ employees
CA ARD has some beautiful features which I haven't found anywhere else. For example, when designing or creating our test cases and doing scenarios, we are able to restrict our flows. If we take a data link between two processes, we can actually restrict it, so that in production, if our functionality breaks down, we can restrict that, and all the flows related to it will be removed from the test data set. That is something we can actually do from CA ARD. View full review »
Thiyagu Shanmugasundaram
Senior Consultant at a tech services company with 5,001-10,000 employees
* Business flow creation * Test case optimization and generation * Risk-based testing * Automation test script creation * Test Data Manager integration The product reduces the efforts required in documenting requirements, test case creation, and automation script generation. Test Case Review was quick and easy, by visually going over the flow. We were able to standardize the automation scripts. View full review »
Automati3096
Automation Engineer at a comms service provider with 10,001+ employees
The modeling, without question. The modeling is a game-changer. View full review »
Software1252
Software Analyst Principal – Activation System Dev at a comms service provider with 10,001+ employees
The ability to provide developers information on how to design the request. View full review »
Jan Van Dravik
Chief Of Architecture & Industrialisation (Agile/Devops Prg Leader) at BNP Paribas
Modeling how the application works, and then getting every use case we can test. Designing the right tests, what are the most critical tests we must do. View full review »

Sign Up with Email