api-test-suite
Install
mayros skill install api-test-suite
mayros skill install [email protected]
10-category API test coverage analysis with gap detection
README
api-test-suite
Generate comprehensive API test suites covering happy path, error handling, authentication, validation, and contract testing.
Installation
Copy this skill directory into your Mayros skills folder:
cp -r skills/api-test-suite ~/.mayros/skills/api-test-suite
Or install via the Skills Hub:
mayros skill install @apilium/api-test-suite
Usage
Activate the skill in your Mayros session and describe the API endpoint you want to test:
Generate a complete test suite for POST /api/v1/users
The skill will produce test cases across 10 categories:
- Happy path -- valid requests returning 200/201/204
- Validation -- missing fields, invalid types returning 400
- Authentication -- missing/expired tokens returning 401/403
- Not found -- non-existent resources returning 404
- Conflict -- duplicate creation returning 409
- Rate limiting -- burst requests returning 429
- Server errors -- fault injection returning 500
- Pagination -- page boundaries, out of range
- Idempotency -- PUT/DELETE repeated safely
- Security -- SQL injection, XSS, path traversal
Coverage Analysis
The skill tracks which categories have been covered and reports gaps:
api-test-suite: 12 test(s) across 7/10 categories | coverage=70% | gaps: rate_limit, idempotency, security
Use the coverage report to ensure no category is overlooked before merging.
Contract Testing
The skill guides generation of response shape assertions that validate:
- Required fields exist in the response
- Field types match the declared schema (OpenAPI 3.x or JSON Schema)
- No unexpected extra fields in strict mode
- Date formats follow ISO 8601
Semantic Predicates
| Predicate | Description |
|-----------|-------------|
| apitest:suite_generated | A test suite was produced for an endpoint |
| apitest:coverage_gap | A test category is missing coverage |
| apitest:coverage_context | Namespace-level coverage state |
License
MIT
Versions
Comments
Sign in to leave a comment.
Loading comments...