Validate text content inside your automated tests
Checking that specific text appears (or does not appear) on a page is one of the simplest and most valuable assertions in test automation. Whether you are verifying error messages, confirming page content after an action, or ensuring that key UI elements display the correct text, the Check Text step lets you do it reliably and clearly.
This step allows your test to look for exact text on the page and assert its presence or absence, giving you confidence that your application not only functions but also communicates correctly to the user.
Why text validation matters
User interfaces are not just about buttons and navigation. They communicate state, status, and outcomes through text:
Success messages after form submission
Error messages when validation fails
Product names and pricing details
Header text and navigation labels
Informational messages and alerts
If the wrong text appears, the user may be confused, misled, or unable to progress. Visual tests alone are not enough—you need to confirm that the expected words are present when they should be, and not present when they should not be.
Clear assertions with minimal effort
The Check Text step lets you:
Define the exact text string you expect
Assert that it appears on the current page
Optionally fail the test if the text is missing
Use this in combination with other actions
This makes it ideal for common validation patterns such as:
“Thank you for your order” appears after checkout
“Invalid credentials” appears after a failed login
“Item added to basket” appears after adding a product
“Profile updated successfully” appears after saving changes
Because this is part of your test flow, it runs precisely when you need it, not as a separate check later.
Works with dynamic content
Many modern sites show text that can include dynamic values such as user names, dates, prices, or counts. You can assert on static portions of text or use patterns that focus on the relevant part of the string.
For example:
Confirm the word “Success” appears somewhere
Assert a message contains expected keywords
Validate a dynamic message while ignoring variable parts
This allows you to build robust checks that are not brittle in the face of inevitable content variation.
Combine with user interactions
Text validation typically follows an action. Because of this, you can chain it with steps such as:
Click element
Fill input
Submit form
Navigate to a page
Wait for content to load
This means your assertions reflect real user behaviour and happen in context rather than in isolation.
Confidence for stakeholders
Text is how your application communicates state. When automation verifies text:
Developers know the system behaved as expected
Testers know UI feedback works reliably
Product owners see correct messaging to users
Stakeholders gain confidence in release quality
It gives everyone clarity, not just pass/fail status.
Predictable, readable tests
Because the Check Text step is explicit and declarative, your flows read like documentation. Instead of guessing what the test is checking, anyone viewing the Flow Designer or test results can see exactly what text was expected.
This makes maintenance easier and tests easier to understand, especially for teams that include less technical stakeholders.
Text matters. And by validating it automatically, you ensure that your user experience remains consistent, correct, and clear.