it-app-e2e-spec-writer

You can generate and update YAML-based end-to-end test specifications from natural-language test scenario requirements. This process organizes scenarios by feature, action, and page area while satisfying the required YAML schema with scenario ID conventions and status tracking.

The required YAML schema mandates specific fields including scenarios, id, category, status, steps, and expect. It enforces scenario ID conventions, step and expect phrasing rules, and precondition key constraints aligned to the target repository.

You maintain precondition catalogs by using only the specified precondition keys from the target repository's fixtures. This ensures the correspondence between fixtures and preconditions remains intact and prevents broken test dependencies during spec updates.

Yes, you can modify or extend existing YAML test specs when designing test cases for changed application features. The specification generation updates step and expect phrasing rules across multiple page-action areas while maintaining schema compliance.

Yes, after creating new YAML scenario files under the specs directory, you must run `npm run gen:index` to update the scenario index. This keeps the test specification catalog synchronized with the newly added or modified E2E test scenarios.

YAML spec generation requires strict adherence to predefined precondition key constraints and target repository conventions. You must not introduce undefined fixture keys, and the test code generation and update process must proceed as a paired set alongside spec changes.