Create Tests
In brief: Create Tests writes SmartTests and related fixtures for requirements, using your connect-to-test-env policy for a runnable environment.
When to use
When you need automation authored for plans/scenarios without necessarily running the full Run QA composite. Also a default subflow of Run QA.
Prompt
/testchimp create tests
/testchimp create tests for plans/stories/checkout
/testchimp create tests for password reset
/testchimp create tests for TestChimp operation id 01HXYZ...
/testchimp create tests for service OpenAPI root path/to/openapi.yaml
Operations UI Create test copies use the for TestChimp operation id … (and field/response-code) forms. See API contract governance.
Scope
Optional. Feature branch → requirements tied to the diff; default branch → since last create-tests (or ask). Or name plans paths / a file list. Or an API operation coverage scope (OpenAPI root, TestChimp operation id, and optional request/query/response field or response code) — agents fetch gaps via CLI/MCP and may update existing UI or API tests (not only dedicated api/ specs).
Policy
Optional create-tests.policy.md for fixture conventions, AI-step usage, and exclusions.
Prerequisites
Depends on connect-to-test-env (Missing config until that policy exists).
What it does
Authors or updates Playwright SmartTests (and fixtures/seeds as needed), bumps @testchimp/playwright to npm latest when the install is behind (so CI lockfiles pick up plugin releases), links scenarios where appropriate, and reports actions with policy version. See SmartTests and runtime plugin.