Dynamic Values, shared config, and real API calls beside your UI steps.
Real journeys need realistic data
Seed and assert 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.
Values Store
Built-in Values
Value style | Behaviour |
|---|---|
Static Values | Stay the same for the whole Test Case |
Dynamic Values | Change each time you use them |
Account Values | Hold URLs, tokens, and JSON fixtures every test can share |
Built-ins | Realistic names, emails, and numbers generated by DoesQA |
API steps and the Value Store carry data through the journey
POST to create a user. Store the response. Fill the registration form with a Value 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.
Part of the platform, not a bolt-on
Values sit beside Mail steps, branching Flows, hosted Runs, and Results. See Email testing, Platform, and Features for related capability.
