How does QA Studio decide who can see or change an application?

Each application belongs to exactly one team, and members of that team work with its applications while everyone else doesn't see them. Every member holds one of five cumulative roles: Admin, Team Lead, Editor, Executor, or Viewer.

What does the health score measure?

QA Studio computes a health score of 0–100 that starts from the pass rate and subtracts a penalty for flaky tests. This keeps an application whose tests flip between pass and fail from presenting a falsely perfect picture.

Can teams share applications with other teams?

Yes. The owning team can grant another team view, execute, or full access. A user's effective permission is the lower of their own role and the grant level, so a Viewer given full access remains view-only.

Large Language ModelsAI Coding AssistantsAmazon AI Blog17h agoOct 29, 2026, 04:00 JST

AWS adds team controls to QA Studio on Amazon Nova Act

Send on LINE

3 Key Points

What happened
AWS added applications and team-based user management to QA Studio, its Amazon Nova Act reference solution, letting each team own its tests and health metrics.
Why it matters
The update organizes tests under applications with owners and access roles, so coverage problems have a clear team to land on as automation spreads across squads.

WHO IT HITSQA platform teams and engineering managers running test automation across multiple squads get per-application health metrics and role-based access, reducing the need to manage permissions on thousands of individual tests.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Get these free every morning

Context & Analysis

QA Studio builds on the natural language test authoring introduced in Part 1 and the test suites and CI/CD integration added in Part 2. As more teams join a deployment, the flat list of tests becomes hard to manage, and the new applications capability gives each team a container for its use cases and suites, with ownership inherited from the application.

Health reporting draws on Amazon CloudWatch custom metrics that QA Studio records for every execution, dimensioned by application and environment. The health view shows pass rate, total executions, and failure count, and a metrics tab offers 7-day hourly or 30-day daily trends. Views for flaky tests and recent failures link back to Amazon Nova Act trajectory logs and session recordings for quick triage.

Access control uses Amazon Cognito groups mapped to roles, enforced at two layers by AWS Lambda and Amazon API Gateway. The same model supports the OAuth client credentials flow from Part 2, so a CI pipeline authenticates as a machine identity with only the scopes it needs.

FAQ

How does QA Studio decide who can see or change an application?: Each application belongs to exactly one team, and members of that team work with its applications while everyone else doesn't see them. Every member holds one of five cumulative roles: Admin, Team Lead, Editor, Executor, or Viewer.
What does the health score measure?: QA Studio computes a health score of 0–100 that starts from the pass rate and subtracts a penalty for flaky tests. This keeps an application whose tests flip between pass and fail from presenting a falsely perfect picture.
Can teams share applications with other teams?: Yes. The owning team can grant another team view, execute, or full access. A user's effective permission is the lower of their own role and the grant level, so a Viewer given full access remains view-only.

Amazon AI BlogRead Original Article

Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Get it free

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.