Accelerating software delivery with agentic QA automation using Amazon Nova Act – Part 3
As QA test automation spreads across an organization, organizing tests and controlling who owns them becomes the real work. Part 3 of the QA Studio series on Amazon Nova Act adds applications that organize tests and report health metrics, plus team-based user management that controls who can see and change what.
As organizations adopt more quality assurance (QA) automation, a new challenge emerges that is unrelated to writing tests. Multiple teams begin to utilize the same test automation platform, leading to hundreds of test cases belonging to different products and squads. This makes it difficult to determine if an application's test coverage is healthy at a glance.
Instead of focusing on test authoring, teams must now concentrate on organizing tests and determining who owns the tests and is accountable for any coverage issues. In the first post, QA Studio was introduced as a reference solution using Amazon Nova Act. Teams could define tests in natural language and run them through AI-powered visual navigation.
In the second post, test suites and a CLI for batch regression testing in continuous integration and continuous delivery (CI/CD) pipelines were added. In this post, two capabilities that help QA Studio scale across an organization are discussed. The first is applications, which organizes tests and reports health metrics. The second is team-based user management, which controls who can see and change what.
Applications function as containers for collections of tests, giving them a home and an owner. Use cases and test suites belong to an application and inherit its ownership. When creating an application, teams provide a name, base URL, and optional environments like development, staging, and production. From the application page, teams can create new use cases directly, add existing ones, and group them into test suites.
QA Studio also provides health metrics for each application, including pass rate, executions, and failure count, with a health score of 0-100. This helps teams quickly identify stable applications versus those that need attention. The metrics tab also offers trends over different time periods and allows filtering by environment.
The second capability, team-based user management, controls access to applications based on teams and roles. Each application belongs to exactly one team, and members of that team work with its applications. Access to applications and their tests is determined by roles, with five levels ranging from Viewer (read-only) to Admin (studio-wide access).
This approach simplifies permission management at the application level instead of individual tests, providing a clear owner and accountability for test coverage.
Written by urgent.news from AWS Machine Learning's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
