Run continuous random fuzzing against API endpoints using Dochia. Use when the user wants to fuzz APIs, discover edge cases through random mutations, run chaos testing, or perform long-running mutation testing on specific endpoints. Also use when the user mentions stress testing, finding crashes, hunting for 500s, or mutation-based API testing. Requires an OpenAPI spec file and a running server.
List available Dochia resources including playbooks, mutators, OpenAPI paths, formats, and profiles. Use when the user wants to discover what test playbooks are available, inspect OpenAPI contract paths, see available mutators and formats, or explore what Dochia can test. Also use before running dochia test or dochia fuzz to help the user pick specific playbooks, paths, or methods.
Replay previous Dochia test runs to reproduce errors, re-validate fixes, or debug specific test failures. Use when the user wants to replay API tests, reproduce errors from a previous run, verify that a bug fix resolves previously failing tests, or re-run specific test cases. Also use after running dochia test or dochia fuzz when the user wants to confirm fixes or isolate flaky failures.
Run comprehensive API testing against OpenAPI specifications using Dochia. Use when the user wants to test APIs, run negative/boundary tests, validate API behavior, check for 5XX errors, run security-focused API tests, or verify input validation. Also use when the user mentions chaos testing, fuzzing playbooks, API hardening, or contract testing. Requires an OpenAPI spec file and a running server. (1 supporting files)
Get detailed explanations of Dochia playbooks, mutators, response codes, and error reasons. Use when the user wants to understand what a specific playbook does, what a 9XX response code means, or get details about an error reason from a Dochia test report. Also use after running dochia test or dochia fuzz when the user asks about a specific result, error, or response code in the report.