Skip to content

Advanced workflows ​

Use these guides when a basic browser/API scenario is working:

TaskGuide
Reuse browser authenticationSessions
Combine API preparation and a browser journeyAPI and UI in one flow
Keep customer/admin logged in independentlyBrowser profiles
Wait for results or retry a failed scenarioWaiting and retries
Mock requests, wait for events or assert downloadsNative command reference
Capture traces/HAR, check accessibility or mount componentsNative browser workflows
Calculate totals, branch or iterate over browser resultsJS/TS helpers in a complete catalog test
Attach an artifact or use runner services inside a reusable actionPlugins
Run in GitHub ActionsNative CI
Drive a canvas or Three.js gameGames
Debug a captured requestDashboard and Replay
Retrieve an OTP with CloudFlowMail
Search tables and act on specific cells or rowsTable and cell testing
Feed microphone audio and verify its transcriptAudio-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

Flowstride is MIT licensed. Flowstride Cloud offers free and paid workspace plans.