test-composer

Automate e2e test portfolio generation by invoking the composer with a journey ID to load the journey map and generate happy-path, error state, edge case, mobile, and data-lifecycle variants. It updates the test repository with new scenarios while ensuring coverage goals are met.

A full Playwright test portfolio includes happy-path scenarios, error states, edge cases, mobile viewport variants, and data-lifecycle variants. It enforces API compliance, stabilization, and documentation steps while using the Steps API to implement the generated tests.

Ensure test coverage completeness by using the composer to orchestrate variant generation across multiple states and viewports. It aligns with stabilization and API compliance workflows, updating the repository with scenarios that meet defined coverage goals.

Yes, you can generate mobile and data-lifecycle test variants by loading an existing journey map. The composer automates variant generation across different viewports and data states, then updates the test repository with the new scenarios.

Yes, you need a specific journey ID to start composing an automated test portfolio. Invoking the process with journey=<id> loads the corresponding journey map, generates the test variants, and updates the repository with the new scenarios.

Use an automated test composer when you need to free your team from manual test scoping for single user journeys. It orchestrates full portfolio generation across multiple states and viewports, enforcing API compliance and stabilization steps automatically.