Capabilities and limits
Flowstride (FS) provides native browser, API, manual-testing and CI workflows. FS runs without an account. Cloud includes free accounts and adds workspace services within your plan limits. Keep your installations current through installation and updates.
| Area | Native behavior | Boundary |
|---|---|---|
| JS/TS helpers | Named imports, async calls, active Playwright page and captured JSON results | A call is one reported step. Use explicit FS actions when the steps should appear individually. 50-car example |
| Fixtures and dependencies | Attempt or worker fixtures, deferred cleanup and producer-to-consumer handoffs | Globals are per worker. A failed producer blocks its consumers. Handoffs |
| Browser engines | Chromium, Firefox and WebKit; explicit installation and selection | WebKit is an engine, not the installed Safari application; see browser compatibility |
| Browser actions | Readable and spatial targets, configurable typing, keyboard and pointer actions, scrolling, history, named tabs, frame scopes and dialogs | Use distinguishable controls. Interaction reference |
| Tables and cells | Search through application controls, indexed table/row/cell targeting, row-scoped actions, cell extraction and assertions | Use record identifiers when rows move; virtualized or paginated records must first be rendered. Examples |
| Audio-to-text testing | Audio-file microphone input, duration-based waiting and rendered transcript assertions in Flowstride and Flowstride Pro | Injection requires Chromium; your application performs transcription. Examples and limits |
| API and UI together | HTTP/GraphQL setup, extraction and browser actions in the same scenario | Browser and direct API clients do not automatically share every credential |
| Structured API | Multipart, form, JSON, text and binary requests, named clients, schema checks and polling | Named clients stay on their configured origin. API reference |
| Retrying assertions | Element state, text/value, attributes, CSS/properties, accessible names, URL/title and storage | Polls the condition; does not repeat the preceding action or API call |
| Independent users | Named browser profiles with separate cookies, storage, pages and permissions | Profiles are local to a flow file; shared backend state remains application-defined |
| Saved sessions | Save/use cookies, localStorage and sessionStorage with origin-aware restoration | A saved session is a snapshot, not a second live user or a complete application-memory capture |
| Network control | Match a request body, delay or route a browser response, and capture, extract or assert browser traffic | Applies to browser traffic in the current profile. Network controls |
| Files | Select project-local files or folders, save browser downloads and verify their contents | Existing download destinations are rejected and file-size limits apply. File selection |
| Data and suite control | JSON, CSV and text fixtures, data rows, seeds, fragments, cleanup, conditional skips and tags | Scenario rows restore runner state. Application writes need their own cleanup. Data and run control |
| Time and functions | Browser clock control, function spies, return/throw stubs and call assertions | Backend time and module-private functions are outside this surface |
| Evidence | Video, screenshots, visual baselines with diffs, traces, HAR and DOM snapshots | Treat captured application content as sensitive. Visual checks |
| Application events | Console output, WebSocket text frames and EventSource messages | Arm observers before the trigger. Event checks |
| Accessibility | axe scans, ARIA capture, exact tree comparisons and reviewed baseline updates | Automated scans are partial coverage; ARIA comparison is not a partial-tree matcher |
| Components | Mount, interact, update and unmount vanilla, React and Vue components | Project framework packages and application providers remain required |
| Retries | Whole-scenario retries, flaky results, strict flaky policy and retained attempt evidence | External side effects are not rolled back |
| CI | Native lifecycle, cancellation, summary/JUnit, matrices, file sharding and complete result merging | Normal CI runners; no shared in-memory state across machines |
| Games | Canvas input, pixel comparisons, state/fixtures, checkpoints and Three.js object selection | Game rules and observable state remain application-defined; qualification is explicit |
| Devices | Desktop, phone and landscape emulation | Emulation is not physical-device certification; some touch/audio paths require Chromium |
| Manual | Canvas design, step details, human execution, defects and local history | No automatic browser execution or canvas-to-DSL converter |
| Cloud | Eligible parallel execution, FlowMail and authenticated workspace services | Credentials, plan limits and service permissions apply |
Playwright and Flowstride's native commands
Flowstride has native commands for trace/HAR workflows, route mocking, network event waits, independent browser contexts, downloaded-file assertions, accessibility/ARIA snapshots and validated browser settings. These workflows do not require a project plugin or a custom runner.
Start with native browser workflows, then use the structured command index for arguments and examples. Waiting and retries explains browser action waiting, polling and scenario retries.
For a custom Playwright action, pass the active page to an imported JS/TS helper. For an extension using SDK services, a plugin can get the same page through sdk.browser.page(). A Playwright Page does not supply the Playwright Test runner's fixture/project system or make every Playwright option a native Flowstride command. Use project helpers for ordinary code and the plugin SDK for services such as runner attachments.
Test data and determinism
When a readable label matches several controls, qualify it by container or position. Generation is random by default. Use a fixed seed for reproducible generated values. Use registered cleanup for disposable server records. Pair visual checks with state assertions for game rules.
Manual product boundaries
Cloud synchronization is not simultaneous canvas co-editing. An assignee text field is not a notification or issue-tracker integration. A saved local run is not a cryptographically immutable audit record. See the manual capability guide before designing a team workflow around those assumptions.
