← Back
Phase 4 of 6 · Every flow is validated
Check
Scan
Each flow the execution changes is validated
Runbook
Then a runbook script is created for each of them
E2E test script
Verifies the runbook
APIREST APIs can be tested with Vitest, Jest, Supertest, Postman, Hurl or any other you prefer.
UIFrontend end-to-end tests can be written with Playwright, Cypress, WebdriverIO, Selenium or any other you prefer.
How it works
- 01 New and changed flows
- A new flow gets a runbook (
/runbooks:create); a changed flow gets its runbook updated (/runbooks:update). - 02 Before calling it done
- Run
/runbooks:list --affected,
then/runbooks:run --affected. - 03 Failing runbooks
- A failing runbook means the work is not done and has to be fixed.