How to use AI API Specification → Test Cases
- Open the tool and paste an OpenAPI snippet or a description of your endpoints.
- Optionally add context (feature description, acceptance criteria, environment) — the more concrete the input, the better the result.
- Pick the options (count, output language, focus) and press the action button.
- Review the structured result in the table, then copy or download it as Markdown, CSV or JSON.
AI API Specification → Test Cases features
- Understands OpenAPI 3 / Swagger 2 snippets (JSON or YAML) and plain endpoint descriptions
- Per-operation cases with request (method, path, headers, query, body), expected status and assertions
- Focus selector: all, positive, negative, auth, boundary or security
- Detected operations table plus Markdown/CSV/JSON export
- Choose English, Arabic or Hindi for the generated text — identifiers, HTTP methods and technical tokens always stay in English.
AI API Specification → Test Cases example
Spec → API tests
Input:
DELETE /lookups/{lookup}/values/{id} → 204 / 403 / 409Output:
API-1 Delete unreferenced value → 204
API-2 Delete as Viewer → 403
API-3 Delete referenced value → 409 with reference count
…Frequently asked questions about AI API Specification → Test Cases
Does it need a full OpenAPI file?
No. A snippet with a few paths or even a plain-text description of the endpoints works; the AI lists the operations it detected so you can confirm the scope.
Is my input stored?
No. Your text is sent to the Mutqan AI service and the structured result is returned to your browser. We do not store prompts or outputs — only anonymous usage counters used for daily limits.
How many generations can I run?
Anonymous visitors get a small daily allowance per network address; registered users get a higher daily quota. The remaining count is shown under every result.
Can I get the result in Arabic or Hindi?
Yes — choose the output language. Natural-language fields are written in that language while identifiers, HTTP methods, paths and other technical tokens stay in English.
Technical notes
Your input is sent to the Mutqan AI service over an encrypted connection; prompts and results are never stored — only anonymous usage counters used for rate limiting.
The AI must answer with strict JSON that is validated against a schema on the server before anything is rendered; malformed answers are retried once and then rejected with a clear message.
The AI never invents endpoints that are not in the contract; when the spec is ambiguous the notes field records the assumption.