DoesQA generates, stores, and passes data inside the same Flow as your UI steps. You do not need a separate fixture library for names, emails, shared config, or API setup.

Built-in Values

Type $ in supported fields and pick built-ins such as $testFirstName, $randomNumber, or $testEmail.

  • test* Values stay the same for the whole Test Case.
  • random* Values change each time you use them.

Account Values and Value Store

  • Account Values under Assets → Values hold shared URLs, tokens, and JSON fixtures.
  • During a Run, Data steps and Integration responses write to the Value Store so later steps can read the same names (for example $createdUser.id in a URL).

API steps in the same Flow

Integration steps (GET, POST, PUT, PATCH, DELETE) call your test API from the hosted runner. Typical pattern: POST to create a user, store the response, run the UI journey, DELETE when finished.

When a dependency needs canned HTTP responses, store the mock service base URL in a Value and call it from Integration steps. Stub definitions stay in the service you already run.

For step-by-step guides, see Test data in DoesQA, Test APIs in a Flow, Seed and clean up with API steps, and Use mock servers with DoesQA.

If a $ value does not resolve in a normal field, check you picked it from the $ list and that the Run Recipe or CI Values for that environment include the name. For Values inside Run browser script steps, see My Value is empty in Run browser script.