AWS describes expanding QA Studio with application management, test metrics and team permissions
The QA Studio reference solution assigns tests to applications and teams, records results in Amazon CloudWatch and calculates a test health score. The expansion described also includes access roles and application sharing between teams.
AWS described an expansion of the QA Studio reference solution, which uses Amazon Nova Act to automate tests. Individual tests and test suites now belong to an application and inherit its owner. An application has a name, a base URL and, optionally, environments such as development, testing and production.
According to AWS, the solution records the results of each run as custom metrics in Amazon CloudWatch, broken down by application and environment. The dashboard shows the success rate, number of runs and number of failures. A score of 0–100 is based on the success rate, with a penalty deducted for flaky tests. Trends can be tracked hourly over seven days or daily over 30 days. The overview of flaky tests assesses alternating successes and failures over the past seven days; recent failures link to execution logs and session recordings from Amazon Nova Act.
Each application belongs to exactly one team. Access to its tests is governed by team membership and one of five roles with progressively broader permissions. An administrator has visibility across teams and applications. The owning team can share an application with another group for viewing, running tests or full access.
Why it matters
The architecture described shows how to link results to a specific application, environment and responsible team as automated testing expands. The penalty for instability in the score helps distinguish consistently reliable tests from those whose results fluctuate.
Two audiences, two different impacts
What this means
For individuals
A tester using QA Studio can go directly from the overview of recent failures to the execution log and session recording, which provide evidence for investigating the error.
For a business
For a business, the main impact is the management of responsibility and access: permissions are set at the application level and also apply to its tests, so there is no need to manage each test separately.
DevelopmentCheck the original
Event sources
only one source so far · 1 publisher, 0 independent. We count feeds from the same owner only once.