aqua saves time with AI and keeps your IT & Tech product clients satisfied

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

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

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

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 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