Exploratory Testing
Run exploratory testing sessions with external users to validate MCP Servers, Agent Cards, and REST APIs through hands-on testing and structured feedback.
Overview
Exploratory Testing lets you create testing sessions, invite external users via email, and collect structured feedback on your agentic assets. Testers interact with your assets through the Protocol Tester and provide pass/fail/in-progress feedback per entity (tool, skill, or endpoint).
Key Features
- Session Management — Create, activate, and manage exploratory sessions with expiration dates.
- Multi-Asset Support — Include MCP Servers, Agent Cards, and REST APIs in a single session.
- Email Invitations — Invite external testers via email with OTP verification.
- Shareable Link — Copy a session link to share with testers.
- Structured Feedback — Testers provide pass/fail status and comments per entity.
- Captured Data — Request/response interactions are automatically captured for review.
- Session Submission — Testers submit their session when done; results feed into A2TF runs.
Creating a Session
- Navigate to Test Lab → Exploratory in the sidebar.
- Click “New Session”.
- Enter a name, optional description, and expiration date.
- Add assets from the tabs: MCP Servers, Agent Cards, REST APIs.
- Each asset requires an environment (e.g. Mocking Service, Staging).
- Invite testers via email from the Users tab.
Adding Assets
MCP Servers
Add MCP Servers to let testers interact with tools, resources, and prompts. Each server must have at least one environment configured.
Agent Cards
Add Agent Cards to let testers interact with A2A skills. Testers can send messages and evaluate responses.
REST APIs
Add REST APIs to let testers interact with endpoints. Each endpoint appears as a testable card with method, path, parameters, and request body fields.
External Tester Experience
When a tester opens the session link:
- OTP Verification — They verify their email with a one-time code.
- Asset List — They see all assets with expandable entity sections.
- Test Dialog — Clicking “Test” opens the Protocol Tester pre-configured for that entity.
- Feedback — After testing, they provide pass/fail/in-progress status and optional comments.
- Submit — When done, they submit the session. Results are recorded as an exploratory run.
Entity Types by Asset
| Asset Type | Entity Type | Displayed As |
|---|---|---|
| MCP Server | Tools, Resources, Prompts | Schema-based forms |
| Agent Card | Skills | Message-based interface |
| REST API | Endpoints | Method + path with parameter forms |
Session Status
Sessions progress through these states:
- Draft — Being configured, not yet accessible to testers.
- Active — Testers can access and submit feedback.
- Completed — All invitees have submitted or the organizer closed it.
- Expired — Past the expiration date.
Viewing Results
Organizer View
The Feedback tab shows results grouped by user and asset:
- Per-user pass/fail/in-progress counts.
- Per-asset breakdown with entity-level feedback.
- Captured interaction data (request/response snapshots).
- Comments from testers.
A2TF Integration
When a tester submits their session, an exploratory run is created in A2TF with:
- Run type:
exploratory. - Individual results per entity with feedback status.
- Request/response snapshots from captured interactions.
View exploratory runs in Test Lab → Runs.
Exploratory Sessions on Asset Pages
Each MCP Server, Agent Card, and REST API detail page has an Exploratory tab that shows:
- Sessions that include this asset.
- Feedback summary for entities of this asset.
- Quick navigation to session details.
Next Steps
- Test Lab — Run and inspect automated and exploratory tests.
- A2TF Testing Framework — Design automated test cases.
- MCP Servers — Create servers to test.
- REST APIs — Create REST APIs to test.
Use Exploratory Testing to gather hands-on feedback from real users on your agentic assets.