# Running Release Tests

Run automated release testing (UI or API) via the AWS DevOps Agent using a...

- Repository: https://github.com/aws/agent-toolkit-for-aws (3366 stars)
- Category: Design
- License: Apache-2.0
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add aws/agent-toolkit-for-aws --skill running-release-tests -g -a claude-code -y`
Codex: `npx skills add aws/agent-toolkit-for-aws --skill running-release-tests -g -a codex -y`
Cursor: `npx skills add aws/agent-toolkit-for-aws --skill running-release-tests -g -a cursor -y`
Gemini CLI: `npx skills add aws/agent-toolkit-for-aws --skill running-release-tests -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add aws/agent-toolkit-for-aws`

## Description

Run automated release testing (UI or API) via the AWS DevOps Agent using a pre-configured test profile. Use when the user wants to validate multi-step workflows, verify features, check for regressions, or test API endpoints. Trigger words include run tests, UAT, test my app, test profile, UI test, API test, automated testing, regression test, QA, end-to-end test, run the QA agent.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Release Testing

> **AgentSpace routing (SigV4 only):** If `list_agent_spaces` is available in your tool list and the multi-space orchestration skill has NOT been invoked yet this session, invoke it first to determine which `agent_space_id` to use. Then pass `agent_space_id` on all tool calls below. For bearer token auth this is unnecessary, the token is already scoped to one space.

Run automated release testing in the cloud via the AWS DevOps Agent's Release Testing Agent. Supports UI testing (browser-based) and API testing (OpenAPI spec-based). Uses pre-existing test profiles that define target URL, agent type, personas, and credentials.

**Input is a test profile**, the test profile already contains the target URL, agent type (UI or API), test personas, and credentials. Do NOT ask the user for a URL directly; the URL is defined in the test profile.

## Prerequisites

- A pre-existing test profile (Knowledge Item ID like `ki-12345`) created from the AWS DevOps Agent console

## Gathering test parameters

Before starting any workflow, you MUST gather the following parameters. Do NOT proceed to job creation until answered.

### Step 1, Test profile (required)

Ask the user which test profile to use. The test profile already contains the target URL, agent type (UI or API), test personas, and credentials configuration, these do NOT need to be gathered separately.

**Note:** A pre-existing test profile is a prerequisite. Test profiles are created using the AWS DevOps Agent console or API, not through this tool. If the user asks whether one can be created here, inform them it must already exist.

### Step 2, Test requirement (optional)

If the user has not already mentioned a test focus, ask:
> "Do you have a specific test requirement or focus area? If not, I'll run a full exploratory test."

Wait for the user's response. If they provide one, use it as the `test_requirement`. If they say no or skip, proceed without it.

The rest: https://github.com/aws/agent-toolkit-for-aws/blob/HEAD/plugins/aws-agents-for-devsecops/skills/running-release-tests/SKILL.md