# Amazon — Accelerating software delivery with agentic QA automation using Amazon Nova Act – Part 3

- Company: Amazon (amazon.com)
- Announced: 2026-10-28T18:12:13+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/accelerating-software-delivery-with-agentic-qa-automation-using-amazon-nova-act-part-3/
- Record: https://forck.live/items/28895-accelerating-software-delivery-with-agentic-qa-automation-using-amazon-nova
- Subject: Bedrock / Nova
- Models affected: Amazon Nova Act

Amazon's third post on QA Studio, a reference solution built with Amazon Nova Act, adds applications and team-based user management so the tool can scale across an organization. An application represents the system under test and gives a collection of tests a home and an owner, so use cases and test suites inherit its ownership instead of sitting in one flat list. Creating an application takes a name, a base URL and optional environments such as development, staging and production. QA Studio records every execution as Amazon CloudWatch custom metrics dimensioned by application and environment, and turns them into a health view with pass rate, execution count, failure count and a 0–100 health score that subtracts a penalty for flaky tests. Teams can chart executions, successes, failures and average duration over a 7-day hourly or 30-day daily window, filter by environment, and open flaky-test and recent-failure views that link back to Nova Act trajectory logs and session recordings. Access is organized around teams, with an application belonging to exactly one team and members holding one of five cumulative roles: Admin, Team Lead, Editor, Executor or Viewer.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/accelerating-software-delivery-with-agentic-qa-automation-using-amazon-nova-act-part-3/:

> As quality assurance (QA) automation adoption grows inside an organization, a new problem appears that has nothing to do with writing tests. A platform team stands up test automation, then a second team wants to join, then a dozen more. Soon hundreds of test cases belong to different products and squads, and everyone can see everyone else’s tests. No one can answer a basic question at a glance: is this application’s test coverage healthy right now? Test authoring stops being the bottleneck. Organizing tests and controlling who can touch them becomes the work.
> 
> A second, related question follows close behind: who owns this application and its tests, and who is accountable when coverage slips? Without a clear owner, health problems have no one to land on.
> 
> In the first post , we introduced QA Studio, a reference solution built with Amazon Nova Act . Teams use it to define tests in natural language and run them through AI-powered visual navigation. In the second post , we added test suites and a CLI for batch regression testing in continuous integration and continuous delivery (CI/CD) pipelines. In this post, we cover two capabilities that help QA Studio scale across an organization.

---

Record: https://forck.live/items/28895-accelerating-software-delivery-with-agentic-qa-automation-using-amazon-nova
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md