Test generation flow

At a high level, generation follows a fixed pipeline per OpenAPI operation.

High-level pipeline

1. Parse OpenAPI The engine parses and fully resolves the OpenAPI model.
2. Build valid case ValidCaseBuilder builds a baseline valid TestCase.
3. Create context TestGenerationContext is created with the OpenAPI model, operation, valid case, and helpers (example value generator, schema merger, budgets).
4. Run providers Providers execute in a fixed order:
5. auth
6. parameters
7. request body
8. Aggregate outcomes Provider outcomes are merged into Outcome<TestSuite>. Budgets and error handling determine whether the result is success, partial success, or failure.
9. Write artifacts An ArtifactGenerator emits outputs (template-based code or JSON/YAML suites).

Outputs

• TestSuite: operation-level container (operationName is the stable identifier).
• TestCase: individual scenario (request inputs + expected status/body).
• GenerationReport: aggregated suites + errors + summary (success/partial/failure/not-tested).

See also:

• Provider-rule model
• Error handling
• Budget controls