THE FLOWSTRIDE HANDBOOK
Write browser and API tests in Flowstride (FS). Call JavaScript or TypeScript for custom checks, inspect each run in the live dashboard, and run the same flows in CI.
Browser & API · Manual flows · Native CI · Browser games
Feature: Order verification
Scenario: API and browser agree
Given "The order exists"
flow.get "/api/orders/FS-101";
flow.expect status "200";
flow.extract resBody "id" as "orderId";
When "The same order is opened"
flow.open "/orders/@orderId";
Then "Its identifier is visible"
flow.expect text "@orderId";CHOOSE YOUR STARTING POINT
Install Flowstride, configure your application, and verify a browser journey. Add API setup when your test needs it.
Write a flowPlan the coverage, map the journey, record outcomes, and hand over a defect someone can reproduce.
Open the manual guideRun your existing flows without a custom runner. Keep clear failure status, reports, and evidence.
Set up native CIDrive a canvas, inspect game state, compare screens, and select live Three.js objects.
Explore game testingFROM A SIMPLE CHECK TO A COMPLETE JOURNEY
Calculate discounts for 50 cars and verify each visible price by SKU.
Create through an API, extract a value and verify the same record in the browser.
Reuse generated credentials and retrieve a delivered code through FlowMail.
Find a row, act inside a cell and carry extracted data into another page.
Move between windows and verify controls inside embedded documents.
Feed a microphone fixture and verify the transcript your application produces.
Select dependent options, set dates and check the exact accepted values.
Keep customer and admin browser profiles independently signed in.
Mock responses, wait for events and verify exported files natively.
Mount a component, check its behavior and inspect accessibility regressions.
Read target and condition results, actual values, call logs and source locations.
Generate once, reuse deliberately and restore origin-scoped browser storage.
Drive input, select objects and verify exposed game state and rendering.
ALREADY UP AND RUNNING?
Go straight to the syntax, behavior, or debugging guide you need.
Capabilities & current limits →