Capture a stored value into your test results
When your automated test runs, DoesQA can store and manipulate values from many different sources — from CI/CD inputs, API responses, dynamic calculations, scraped data, custom code nodes, or entries in the Value Store. The Debug Value step lets your test capture the current value of any stored value and attach it directly to your test results.
This makes it easy to see exactly what data your test was working with at a given moment, helping you troubleshoot flows, confirm assumptions, and understand how values change as the test progresses.
Why capturing values helps
Tests often depend on values generated earlier in the flow:
Tokens from authentication responses
IDs or keys from API calls
Dynamic values calculated during execution
Extracted fields from UI or API responses
Inputs passed from CI/CD or recipes
Values stored earlier in the Value Store
When something goes wrong — or when you want deeper insight — simply logging the value in the results lets you see what the test actually had in memory.
Without this step, you might only see a pass or fail, making it harder to diagnose failures or understand value progression.
What kinds of values you can debug
The Debug Value step can capture values from:
The global Value Store
Dynamic values generated on the fly
Values passed in via CI/CD or recipes
Results of custom code nodes
Fields extracted from APIs or tests
Session data that was stored earlier in the run
This makes it a flexible tool for capturing context, not just test result flags.
How it works in your test
When this step runs:
You specify the value name or key you want to capture
DoesQA retrieves the current value from memory
The value is included in the test results output
This means when you review results later — inside your dashboard or exported logs — you can see not just pass/fail, but what the test saw at that moment.
When to use Debug Value
This step is valuable when:
You need to confirm dynamic data is correct
A test is failing and you want more detail
You’re building a new flow and want visibility
Values influence later steps
You want context in shared test results
You’re validating API responses or parsed content
For example:
After calling an API, debug the returned token
After custom code execution, capture the computed value
After extracting a field from UI, output it to results
After a recipe injection, confirm the input value is present
Seeing values directly in results eliminates guesswork and accelerates iteration.
Combine with assertions for clarity
Debug Value works well alongside other steps such as:
Check Value to assert expected content
Run Browser Script to manipulate or extract values
Integration API GET to retrieve backend data
Sleep or Wait for Element for timing
Visual regression for layout context
By pairing debug output with assertions, you create tests that not only validate behaviour but explain it.
Capturing stored values in your results turns your automated tests into rich, understandable sources of truth rather than simple pass/fail signals.