Test data and APIs in one Flow
Dynamic Values, shared config, and real API calls beside your UI steps.
Real journeys need realistic data.
DoesQA gives you Values, a Value Store, and Integration API steps in the same Flow as the browser. Generate names and emails with built-ins. Share secrets from Assets. Call your API to seed data, then run the UI journey against a working backend.
Built-in Values
Type $ in supported fields and pick built-ins such as $testFirstName, $randomNumber, or $testEmail. Built-ins generate realistic names, emails, and numbers as part of DoesQA.
test* Values stay the same for the whole Test Case. random* Values change each time you use them. Account Values under Assets → Values hold URLs, tokens, and JSON fixtures every test can share.
API steps and the Value Store carry data through the journey.
POST to create a user. Store the response. Fill the registration form with $testEmail or a field from the stored JSON. Check the backend with GET or JSON asserts. DELETE when the test finishes.
When a dependency needs canned HTTP responses, point Integration steps at the mock service you already use. Store its base URL in a Value. DoesQA integrates cleanly with external mocking services without owning your stub definitions.
Hands-on guides: Test data in DoesQA, Test APIs in a Flow, Seed and clean up with API steps, Use mock servers with DoesQA.
Part of the platform, not a bolt-on.
Values sit beside Mail steps, branching Flows, hosted Runs, and Results. One product. One place to maintain the journey.
