QA Studio Adds Team-Based QA Test Organization, Metrics, and Access Control
QA Studio, built with Amazon Nova Act, now supports organizing tests by application, provides new metrics dashboards, and introduces team-based user management with role-based access and cross-team sharing.
What changed?
QA Studio has introduced several capabilities to help organizations scale QA automation. Tests can now be organized inside 'applications,' each with a clear owner and set of test cases. The platform now reports health metrics such as pass rate, test executions, and a computed health score at the application level, using Amazon CloudWatch. Teams gain the ability to manage users through team-based roles (Admin, Team Lead, Editor, Executor, Viewer), and applications can be shared between teams with access levels that combine team role and shared permissions.
Why does it matter to an everyday developer?
For developers working in larger organizations, these updates directly address common pain points in test automation at scale. Instead of a single flat test list, teams can focus on their own applications and assigned tests. Health metrics and dashboards allow rapid assessment of test suite stability, identifying flaky tests and recent failures quickly. The new team-based roles ensure that only the right people can view or change tests, reducing accidental changes or confusion about ownership, while cross-team sharing enables collaboration where needed without overexposing controls.
What can the developer do now?
Developers can organize their QA tests by application, assign ownership, and view real-time and historical metrics to monitor release readiness and test reliability. Teams can safely onboard more members by assigning granular roles, improving governance. Cross-team projects can be supported by sharing applications at the required access level. Administrators and team leads can audit and manage access centrally, and developers can act on health metrics to proactively improve quality.
