The QA Agent covers the testing lifecycle in the same project as the stories it tests, so coverage tracks requirements instead of drifting from them.
Surfaces
| Surface | What it’s for |
|---|---|
| Test Sheet | Fast, spreadsheet-style editing of cases |
| Test Dashboard | Run status and QA reporting |
| Test Plans | Grouping suites for a release or sprint |
| Test Repository | Suites and reusable test cases |
| Automated Testcases | Cases promoted to automated execution |
| Test Environments | Where a run executes |
| Load Testing | Performance runs |
| Test VAPT | Vulnerability assessment and penetration testing |
Generating cases from stories
Rather than writing a suite from scratch, generate test cases from a user story — the case inherits the story’s acceptance criteria, and a requirement change is visible as a case that needs updating.
Fixed bugs can be turned into regression cases the same way, so a defect can’t silently come back.
Cloud scans
Under More, Studio scans connected cloud accounts for misconfiguration:
- Cloud Providers — the accounts you’ve connected.
- Cloud Scans — scan runs.
- Cloud Findings — what they turned up.