Test Management Tool For SaaS & Tech Companies

IT company with 9-digit valuation detects 98% of major defects through proper testing

A software development company in Germany struggled to continue releasing features every two weeks while keeping the app stable. The internal QA solution offered little continuity between tickets, which made issues slip.

aqua helped organise regression testing to improve the efficiency of QA specialists while reducing time spent on regression testing by 34%

aqua has helped over 30 enterprise IT product companies level up their QA

Our work with the client started with a QA audit to identify the biggest bottlenecks in the workflow and the challenges behind them. Below are the initial findings

Testing efficiency

The QA team struggled to see if they are keeping up with QA tasks. Similarly, the team lead could not see if there is extra capacity for individual testers or the entire team.

Adding task overviews and planning visualisation to the internal QA tool would distract developers from the main product

Progress visualisation

For our client, QA often was the bottleneck for the features requested by the product owner and just implemented by the developers.

It was impossible to tell when QA clears the feature for production without nagging the QA lead all the time

Poor communication

Tracking issues locally blocked proper communication between fellow testers and the development team. Issues would get lost as somebody goes on vacation. Developers would not know they need to fix a particular bug.

The lack of written communication across reproducing and solving the bug led to redundant effort in tech product testing

Test hierarchy

Like most product companies, our client needed to run a lot of integration testing to ensure all components work properly. Pinpointing when exactly the app breaks is vital to isolate issues, too.

The internal QA tool lacked hierarchy-related functionality to keep up with all the integration testing scenarios

Regression testing

While new features breaking existing functionality is part of the process, our client could not afford it to happen on production.

The nature of the service meant that monthly subscribers would cancel their subscription over disruption

Key aqua features that save time and money for SaaS & Tech companies

aqua helped the client ditch their outdated internal QA tool to optimise a wide range of testing procedures, make the process transparent and synchronise development

AI to test faster than ever

Open a requirement and auto-create an entire aqua test case covering it. Describe a test in plain words and get full test steps for it. Auto-prioritise your test cases to see which tests you absolutely must execute before deploying

Agile board

aqua allows you to run the QA effort just like modern companies run their development. Our software supports a Planning Board overviewing all tasks across sprints, Scrum Board to plan individual sprints, and Burn-Down Charts to see how your testers progress.

Both testers and their Lead can see where they stand and hold each other accountable to the scope of work and ability to meet it. aqua is a perfect tool for tech companies' new features testing

QA dashboards & reports

Increasing testing transparency is beneficial for non-QA employees, too. This is why aqua offers dashboard functionality providing a quick testing overview for anyone at the company. For example, Product Owner may notice an abnormal churn rate on iOS, confirm that it coincides with a spike in bugs of the iOS client, and ask Project Manager to escalate fixing them.

aqua’s reporting functionality requires even less effort to keep track of QA effort. You can use one of our templates or take time — once — to configure a custom report, schedule it to generate a new version every x days and automatically receive it in your inbox

Collaborative testing

Our software is packed with functionality that cultivates communication and helps you keep everything in writing. Each ticket has a comment section to discuss progress on reproducing bugs or adjusting a test case. Individual team members can be nudged to take a look at a particular item. Users can opt to receive notifications when a particular ticket changes status, e.g. a test case just failed. Software development has long been collaborative, and aqua does the same for testing in IT companies

Testing organisation

aqua helps you organise all tickets to quickly find the relevant ones. You can distribute requirements, test cases, test scenarios, and bugs across multiple testing projects. They are further split into folders. This level of detail helps you run through essential tests first to quickly deploy a new feature or hotfix without breaking the product.

Your testers can also save time with our Views functionality. It is a preset of filters that can be configured once to display all tickets fitting certain criteria later. Once set up, it will take testers one click to see critical issues assigned to them, while the QA lead will easily browse all failed test scenarios.

All items can also be bound by a workflow. For example, you can set up bugs to go the route of Create > New > In Progress > Solved > Closed <> Delivered. It is also possible to make certain fields mandatory when creating a ticket, e.g. they all must have priority, be assigned to someone and/or be placed into a certain sprint

Test scenarios and dependencies

Test scenarios are vital for regression testing, since it requires a thorough sweep of existing code. aqua’s test scenarios are dynamic, as they reference test cases instead of duplicating them once. It means that your regression (or any other) test scenarios are always up to date relative to changes in the test cases.

Dependencies block progression of a test scenario if some of the test case(s) have failed. This is how you avoid product-breaking issues making it into the live product: no update is pushed unless the essential test scenario(s) is all green

AI to test faster than ever

Open a requirement and auto-create an entire aqua test case covering it. Describe a test in plain words and get full test steps for it. Auto-prioritise your test cases to see which tests you absolutely must execute before deploying

Agile board

aqua allows you to run the QA effort just like modern companies run their development. Our software supports a Planning Board overviewing all tasks across sprints, Scrum Board to plan individual sprints, and Burn-Down Charts to see how your testers progress.

Both testers and their Lead can see where they stand and hold each other accountable to the scope of work and ability to meet it. aqua is a perfect tool for tech companies' new features testing

QA dashboards &
reports

QA dashboards & reports

Increasing testing transparency is beneficial for non-QA employees, too. This is why aqua offers dashboard functionality providing a quick testing overview for anyone at the company. For example, Product Owner may notice an abnormal churn rate on iOS, confirm that it coincides with a spike in bugs of the iOS client, and ask Project Manager to escalate fixing them.

aqua’s reporting functionality requires even less effort to keep track of QA effort. You can use one of our templates or take time — once — to configure a custom report, schedule it to generate a new version every x days and automatically receive it in your inbox

Collaborative testing

Our software is packed with functionality that cultivates communication and helps you keep everything in writing. Each ticket has a comment section to discuss progress on reproducing bugs or adjusting a test case. Individual team members can be nudged to take a look at a particular item. Users can opt to receive notifications when a particular ticket changes status, e.g. a test case just failed. Software development has long been collaborative, and aqua does the same for testing in IT companies

Testing organisation

aqua helps you organise all tickets to quickly find the relevant ones. You can distribute requirements, test cases, test scenarios, and bugs across multiple testing projects. They are further split into folders. This level of detail helps you run through essential tests first to quickly deploy a new feature or hotfix without breaking the product.

Your testers can also save time with our Views functionality. It is a preset of filters that can be configured once to display all tickets fitting certain criteria later. Once set up, it will take testers one click to see critical issues assigned to them, while the QA lead will easily browse all failed test scenarios.

All items can also be bound by a workflow. For example, you can set up bugs to go the route of Create > New > In Progress > Solved > Closed <> Delivered. It is also possible to make certain fields mandatory when creating a ticket, e.g. they all must have priority, be assigned to someone and/or be placed into a certain sprint

Test scenarios and
dependencies

Test scenarios and dependencies

Test scenarios are vital for regression testing, since it requires a thorough sweep of existing code. aqua’s test scenarios are dynamic, as they reference test cases instead of duplicating them once. It means that your regression (or any other) test scenarios are always up to date relative to changes in the test cases.

Dependencies block progression of a test scenario if some of the test case(s) have failed. This is how you avoid product-breaking issues making it into the live product: no update is pushed unless the essential test scenario(s) is all green

Traceability

Many companies can track bugs and test their software development fine without a pro-tracking system. But aqua brings full traceability to your organisation and helps you to find answers to the most important questions in a matter of minutes:

01

Is this requirement tested at all/ tested enough?

02

Who did test that and how?

03

What did they do exactly to verify it works?

04

With what kind of data? User inputs?

05

What version have they tested, in which browser & OS?

06

Have the test cases been reviewed and possibly updated after the requirement changed?

07

What defects have been found? Have they been retested? How exactly have they been retested?

08

Who did change the requirement? What has been changed?

“At aqua, we've helped world's most innovative teams optimise their testing process for 20+ years already.”

Paul Elsner CSO at aqua