Advanced workflows
Use these guides when a basic browser/API scenario is working:
| Task | Guide |
|---|---|
| Reuse browser authentication | Sessions |
| Combine API preparation and a browser journey | API and UI in one flow |
| Keep customer/admin logged in independently | Browser profiles |
| Wait for results or retry a failed scenario | Waiting and retries |
| Mock requests, wait for events or assert downloads | Native command reference |
| Capture traces/HAR, check accessibility or mount components | Native browser workflows |
| Calculate totals, branch or iterate over browser results | JS/TS helpers in a complete catalog test |
| Attach an artifact or use runner services inside a reusable action | Plugins |
| Run in GitHub Actions | Native CI |
| Drive a canvas or Three.js game | Games |
| Debug a captured request | Dashboard and Replay |
| Retrieve an OTP with Cloud | FlowMail |
| Search tables and act on specific cells or rows | Table and cell testing |
| Feed microphone audio and verify its transcript | Audio-to-text testing |
Application concerns remain explicit
Keep fixture preparation, teardown and business-specific assertions in your project. Native orchestration removes the need for a custom CI runner; it cannot invent your application's data model or decide what makes a game action correct.
Avoid relying on implementation details
Flowstride (FS) accepts ordinary JS/TS named exports through flow.call. Request page as the first argument for custom browser work. SDK plugins additionally expose runner services such as attachments. Both approaches keep the runner in charge of browser lifecycle and reporting. Check capability boundaries before assuming parity with Playwright Test.
Workflow guides
Targeting · Forms and dates · Tabs and iframes · Email OTP · Assertions and diagnostics · Included runnable examples
