Folders

Folders as feature suites

Name a folder after the feature, not after a date or a person. Example: a Checkout folder that holds:

• Login
• Add to cart
• Pay

Each item is its own journey. The folder is how you say “this is the suite.”

Select and run, fail-fast

Pick the flows to run. They execute in order. If login fails, payment does not start. That is the point of fail-fast: you debug the first break instead of watching later journeys fail because the session never existed.

What to put together

Group journeys that share a setup and a product surface. Keep a smoke path short. Keep an edge-case journey out of the happy-path folder if you do not want it in every run.

Still local

Folders live in this browser with the flows. There is no shared project, no role-based access, no cloud run. If you need a team test-management tool, this extension is not that — and does not try to be.