- Home
- Skills
- Testing & Debugging
- traceable tests
traceable tests
Generate traceable test scenarios, cases, and traceability matrices with mandatory 7-dimension edge-case coverage.
$5
Works with the AI Agents you already use
traceable tests
Example session with this skill installed
I need to write test cases for a new user registration feature. It requires email, password, and a profile photo. Check all edge cases.
- Read your context and instructions
- Compiled the traceable tests
I have analyzed the user registration feature. Following the traceable-tests workflow, I have defined the initial scenarios for your approval.
Test Scenarios
| Scenario ID | Scenario Description |
|---|---|
| TS-REG-01 | User Registration: Account creation, validation, and persistence |
| TS-REG-02 | Profile Setup: Image upload and metadata attachment during signup |
Next steps
- Approve these scenarios or suggest modifications.
- I will then derive the Test Cases using fail-first ordering across the 7 mandatory dimensions.
Once approved, I will generate the full TC table. For example, for TS-REG-01, the cases will include:
| Scenario ID | Test Case ID | Scenario Description | Test Steps | Expected Result |
|---|---|---|---|---|
| TS-REG-01 | TC-REG-01 | Register with null email.<br><br>Precondition: User not in DB. | 1. Submit form with empty email field.<br>2. Submit ValidPass123!. | 400 - email is required. |
| TS-REG-01 | TC-REG-02 | Register with invalid email format.<br><br>Precondition: None. | 1. Enter plainaddress in email field.<br>2. Submit form. | 422 - invalid email format. |
| TS-REG-01 | TC-REG-03 | Register with existing email.<br><br>Precondition: user@example.com exists. | 1. Enter user@example.com.<br>2. Submit form. | 409 - email already registered. |
| TS-REG-01 | TC-REG-04 | Register with valid data.<br><br>Precondition: Unique email. | 1. Enter new@example.com.<br>2. Submit form. | 201 - account created successfully. |
Next steps
- Review the fail-first ordering (negative cases before happy path).
- Confirm if any specific boundary values (e.g., password length) should be added to TC-REG-05.
Connects securely to your tools. The creator never sees your data.
About this skill
Testing often focuses on the happy path, leaving critical edge cases for production. Manual test planning is slow, prone to gaps, and usually lacks clear mapping between requirements and code. This skill enforces a structured three-layer workflow to ensure no dimension of a feature goes untested.
What it does
- Multi-layer documentation generates linked Test Scenarios, detailed Test Cases, and a Requirements Traceability Matrix (RTM).
- Mandatory coverage audit checks every scenario against seven dimensions including null inputs, invalid formats, boundaries, and auth permissions.
- Fail-first ordering prioritizes negative and edge cases in the test suite to catch failures early.
- Traceability mapping creates a direct link from business requirements to specific test IDs and implementation stubs.
- Coverage auditing analyzes existing test code to find orphaned documentation or undocumented implementations.
How it works
- Scenario Generation: The skill analyzes your feature or code to produce high-level Test Scenarios (TS) for your approval.
- Case Derivation: Once scenarios are approved, it generates detailed Test Cases (TC) with specific preconditions, steps, and expected status codes.
- Traceability & Code: It builds the RTM to map requirements and provides structured test-code stubs compatible with your chosen framework.
Frameworks & tools
This skill is language-agnostic. It provides structured guidance for Jest, Vitest, Pytest, Go, .NET xUnit, and RSpec.
Why this beats prompting it yourself
Standard prompts often miss edge cases like unauthorized access or boundary values. This skill enforces a strict 7-point checklist for every single scenario, ensuring a consistent ID system that links your documentation directly to your test suites.
Use cases
- Feature onboarding to design a full testing strategy for a new API endpoint or module.
- Compliance audits to prove requirement coverage with a generated RTM.
- Legacy cleanup to audit existing test files for missing negative coverage dimensions.
- Refactoring to ensure test cases stay synced with updated business logic.
Known limitations
Does not execute tests or generate mocks. It focuses on design, documentation, and code structure rather than performance or load testing.
Requires manual approval at gates before artifact generation. Does not perform UI automation, performance testing, or mock/stub implementation.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 10 days ago
Permissions
No special permissions declared or detected