Validate values of inputs and form elements
User forms are core to most web applications. Whether users are entering usernames, choosing options from a dropdown, typing a search term, or filling out a purchase form, the values inside inputs and fields matter. The Check Value step lets you assert that an input, dropdown, or other form element holds a specific value at a given point in your test.
This gives you confidence that your application not only accepts input correctly but also preserves, displays, or processes values exactly as expected.
Why checking values matters
End-to-end tests often simulate how a user interacts with the interface. Many flows depend on multiple form fields being filled correctly and retaining the proper values as the user navigates the site. Common examples include:
Username or email in login and signup forms
Quantity and option selections in shopping carts
Search input reflecting the query you typed
Form fields prepopulated with user data
Confirmation inputs showing expected values
If a field contains the wrong value—or no value at all—downstream behaviour may fail, and users could be blocked from completing their intended actions.
Clear, precise assertions
The Check Value step lets you:
Select an input or form element
Assert that its value matches an expected string or pattern
Fail the test if the value does not match
Display readable results in your test report
This makes it easy to confirm that the user interface is behaving predictably.
For example:
After filling a form, confirm the input shows exactly what you entered
After a page reload, confirm user preferences persist
After a filter action, confirm the search box shows the chosen criteria
After navigating backward, confirm the previous state remains
Because this is part of your flow, these checks happen exactly where they matter, not as separate post-run validation.
Dynamic values and stored data
Modern web sites often populate input values dynamically, based on user identity, environment, or prior test steps. The Check Value step works seamlessly with DoesQA’s dynamic and stored values system.
You can:
Use values generated earlier in the flow
Compare fields against environment-specific data
Validate dynamic defaults
Confirm query parameters are reflected in form values
This allows you to build robust assertions around behavior that changes from run to run.
Combine with user interactions
Value checks are most powerful when paired with actions like:
Fill input
Select dropdown
Click button
Submit form
Navigate to a page
This means your test reflects true user behavior, checking that not only did you perform the action correctly, but that the application state reflects it as expected.
For example, after filling a field and submitting a form, you can check that the next page shows the correct summary, or that the original input was preserved when navigating back.
Confidence across form-heavy flows
User frustration often arises from subtle UI bugs like:
Inputs clearing unexpectedly
Misleading placeholder text
Incorrect defaults
Search terms not persisting
Filters not registering
By asserting on values directly, you catch these issues reliably before they affect real users.
You also make your test results richer and more meaningful for:
Developers diagnosing issues
Test engineers validating edge cases
Product owners verifying behaviour
Stakeholders reviewing release quality
Value matters. And by checking it automatically, you help ensure your application communicates state correctly and reliably throughout user journeys.