Docs

  • Quickstart

    One command, npx stresseur init, from your app to API tests that pass and run in CI.

  • Record flows

    Record real API calls from your app in development and turn them into YAML flows.

  • Run flows locally

    Run a flow once, as a CI-style repeated run, or as a local load test.

  • CI setup

    Run your flows on every pull request with GitHub Actions and the Stresseur GitHub App.

  • Reading results

    How Stresseur decides a flow got slower, and what the steps and runner noise mean.

  • Gates

    Decide when a slower flow warns or fails the pull request check, in api-tests/stresseur.yml.

  • AI checks

    Check an AI endpoint's answers, speed and token use with expect:, and see pass rates against main on every pull request.

  • Load tests

    Load profiles in api-tests/stresseur.load.yaml, environments, domain verification and plan limits.

  • Test engineer

    Ask @stresseur on a pull request or issue why a flow is slower or failing, to test a change, or to load test it.

  • CLI reference

    Every npx stresseur command and flag, from the published CLI (stresseur 0.4.0).

  • Plans & limits

    What each plan includes. Priced per workspace, not per member.

  • Security

    What leaves your machine, what is masked, and how CI authenticates.