This is our first such solution.

We decided to use this solution to bring in automation and a tool to help the testers.

We were previously just using Excel. We were maintaining all the details there and via a tool called Micro Focus ALM. We used to actually own that tool. We used to put all our requirement details into Micro Focus ALM and then switch over from Micro Focus ALM to Jira. We were looking for a tool where we could actually maintain or manage requirements all in one place.

We utilized HP UFT”. “We changed toll sets when we changed to a model based testing strategy”. In addition we moved away from HP UFT in favor of a Selenium, Java, TestNG framework. This allowed for more integration with addition toolsets and allows for a more open and flexible framework and test harness.”

I was involved in the initial acquisition so I came to CA World two years ago and found the product and brought it back and then we piloted and then we rolled it out to the larger team.

We used another test modeling solution. ARD has better integration with automated test scripting and with test data management. We also switched to it because we were looking for ways to make testing more effective and more efficient; reduce defect leakage.

I have not previously used a test case design tool.

The company was just using ALM for our test management: creating manual test cases, designing and planning, requirements, and traceability. 

My CA representative and I were talking about a problem I was having and he described to me how this tool could help with it.

This was a problem that we were having independent of CA products. It was a problem that we were having in our testing space. This was a tool that we weren't actively using but helped to resolve that issue.

I didn't previously use another solution.

We are a large legacy company with a lot of legacy software. Converting to DevOps and agile, obviously, we had to get faster to the market. Our mind was already wrapped around how we enable teams. When we found the solution that fit nicely into where we are trying to go with our development process overall, it just kind of evolved. 

Well right now we use multiple systems. For example, if you want to build your business diagram, you have to use Visio. You can’t export the diagram into a format useable by Agile Requirements Designer. You need to go directly to an application lifecycle management system and build your steps, but you need follow the business diagram you created in Visio to be able to create those steps for those test cases.

So you have to upload all your requirements into an ALM system to be able to identify your metrics. But with this tool, I see the benefit that you can actually do it automatically. To be able to identify all scenarios, you need to test.

We hadn't used model-based testing tools before.

We sought out this solution because we needed to automate our regression test cases. Application SMEs without automation scripting experience were our main challenge.

When we got introduced to ARD, we did a PoC and realized the benefits. Then, we implemented ARD in our projects.

We're using BPT from HPE ALM. It was not from me, the direction, but I think my leadership saw the opportunity of shifting to the model-based testing, and to have a more connected way to work the requirements. So that was the driving force to the shift.

It was just user stories in an agile environment. Not very good.

Previous to this solution, we just used manual processes.