workflow-action-editor-quality-gate

You validate workflow editor configurations by running build-time checks, unit tests, and Playwright end-to-end tests to verify action-catalog discovery and parameter-schema integrity, preventing UI regressions before deployment.

Playwright testing executes end-to-end verification against schema-driven UI components to ensure the workflow editor correctly maps form-backed fields to backend schemas, catching integration regressions that unit tests miss.

Yes, you need local .NET and Node.js environments to execute the build, unit test, and Playwright verification scripts that constitute the workflow quality gate validation suite.

Ensuring Umbraco workflow action catalogs meet accessibility standards involves running Storybook CI and keyboard-navigation tests to verify the editor remains WCAG-compliant and usable for all content authors.

Workflow editor action configurations fail after adding new form-backed fields when the UI components do not correctly map to backend schemas, which this quality gate detects through parameter-schema integrity validation.

Yes, you can run the quality gate checks sequentially in a CI pipeline by executing the defined build, unit test, Storybook, and Playwright commands to validate stage-transition inspector contexts and action-catalog metadata.