Flowstride QA Playbook

    1

    Write, run, and debug readable Flowstride tests with your coding agent. Includes a complete assertion reference and a runnable lab for browser, API, and CI workflows.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Flowstride QA Playbook

    Example session with this skill installed

    Write a Flowstride test using the included Order Lab. Create and approve a test account through the API. In the browser, verify that a wrong code leaves the protected page inaccessible. Then enter the code from the lab inbox, confirm the signed-in email matches the test account, and register cleanup for that account.

    • Read your context and instructions
    • Compiled the flowstride qa playbook

    Account verification test

    This flow creates and approves a disposable account through the lab API. It checks that a wrong code is rejected and the protected page still requires verification. It then uses the issued code from the local test inbox and checks that the account page shows the exact email created during setup. Registered cleanup deletes the temporary account after the scenario.

    Feature: An approved test account verifies its own sign-in
    
    Scenario: Reject the wrong code and open the verified account after the issued code
    Tags: accounts, otp
      Given "An approved example.test account is prepared by API"
        flow.api.request {
          "method": "POST",
          "url": "/api/qa/accounts",
          "json": { "email": "$randomEmail@example.test" }
        };
        flow.expect status "201";
        flow.extract resBody "id" as "accountId";
        flow.cleanup.register { "method": "DELETE", "url": "/api/qa/accounts/@accountId" };
        flow.extract resBody "email" as "accountEmail";
        flow.api.request { "method": "POST", "url": "/api/qa/accounts/@accountId/approve" };
        flow.expect status "200";
        flow.expect resBody "approved" equals "true";
        flow.open "/verified-account";
        flow.expect visible "Verification required";
    
      When "The buyer requests a code and types a deliberately wrong value"
        flow.open "/verify";
        flow.type input "Test email" "@accountEmail";
        flow.click button "Request code";
        flow.expect visible "Code requested";
        flow.network.arm { "name": "wrong-code", "url": "**/api/account/verify-code", "method": "POST" };
        flow.passcode input "Verification code" "000000";
        flow.click button "Verify";
        flow.network.wait { "name": "wrong-code" };
    
      And "The rejected attempt remains on the verification page"
        flow.network.expect { "name": "wrong-code", "status": 200, "path": "verified", "equals": false };
        flow.expect visible "Code rejected";
        flow.assert.that { "condition": "url", "matches": "/verify$" };
    
      When "The buyer enters the value from the loopback test inbox"
        flow.open "/verified-account";
        flow.expect visible "Verification required";
        flow.api.request { "url": "/api/qa/accounts/@accountId/inbox" };
        flow.expect status "200";
        flow.extract resBody "code" as "otpCode";
        flow.open "/verify";
        flow.type input "Test email" "@accountEmail";
        flow.passcode input "Verification code" "@otpCode";
        flow.click button "Verify";
    
      Then "The protected page shows the very same account"
        flow.assert.that { "condition": "url", "matches": "/verified-account$" };
        flow.expect visible "Account verified";
        flow.expect visible "Signed in as @accountEmail";
    

    Run the example

    Run the example from the Order Lab directory with Flowstride and the matching browser installed.

    npx --no-install flowstride run flows/07-account-verification.flow --browser chromium --ci
    

    The example passed on Chromium, Firefox, and WebKit with Flowstride 1.0.25 and Flowstride Pro 1.0.19. The inbox and account are local lab fixtures.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Turn acceptance criteria into readable .flow tests for your application. The playbook guides your coding agent through inspecting an existing project, choosing stable targets and meaningful assertions, preparing disposable test data, and explaining failures with evidence.

    What’s included

    • Agent playbook for writing, reviewing, and running Flowstride tests using the project’s engine, language rules, and configuration.
    • Nine references covering browser and API testing, network events, accessibility, visual checks, components, games, manual testing, and CI. The assertion reference gives an example for each of the 24 browser conditions and eight stored-value operators.
    • Seven runnable Order Lab flows for order persistence, data-driven totals, network mocks and exports, independent sessions, delivery events, browser scope, and account verification. Separate exercises let you reproduce a soft failure and inspect a visual diff.

    How you can use it

    Ask your agent to write a checkout flow that checks the receipt and verifies the same order in the API. Or give it a failing CI run and ask for the first failed assertion, the expected and observed values, and a command to reproduce it.

    The included lab runs with the open-source Flowstride engine. The suite passed on Chromium, Firefox, and WebKit with Flowstride 1.0.25 and Flowstride Pro 1.0.19. Connected features use your Flowstride workspace and its entitlements.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.

    The playbook covers web applications, browser games, and HTTP APIs. Examples for other applications must be adapted to their UI, endpoints, and test data. The Order Lab uses local fixtures. FlowMail, Cloud reporting, and eligible parallel runs depend on the connected Flowstride workspace.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed today

    Software
    Node.js 22.12 or laterflowstridePlaywright

    Use the browser binary that matches your installed Flowstride engine. The included Order Lab runs locally with the open-source npm package and uses synthetic accounts and orders.

    Permissions

    Read Files
    Browser
    Network Access
    Write Files
    Terminal / Shell
    Environment Variables

    The agent reads the selected project’s tests and configuration, then writes tests and local evidence there. Test execution uses the terminal and browser. Network access is used for setup and the application or API under test. Use project-provided environment variables for configuration and authorized test credentials.

    Listedtoday

    What's inside

    Frequently Asked Questions

    A SKILL.md playbook, nine reference guides, and seven runnable Order Lab flows. The package includes every browser object assertion condition and stored-value operator, plus soft-failure and visual comparison exercises.

    Use Node.js 22.12 or later, the Flowstride engine, and its matching Playwright browser binary. Your coding agent needs access to the test project and terminal to write and run the tests.

    Yes. The playbook guides your agent to check the installed version, use the project’s existing configuration and grammar, and reproduce a specific failure before expanding the run.

    The lab and core browser, API, accessibility, and visual checks run with the open-source Flowstride package. FlowMail and Cloud reporting use an eligible connected workspace. Pro parallel runs follow workspace limits.

    Yes. Flowstride’s native --ci flag runs headlessly and writes JSON and JUnit reports. The playbook also covers browser selection, tags, sharding, and how to trace a failure back to its source step.

    New in Testing & Debugging