Thanks for the post and question. WebUI records test as close as possible to how a user would interact with the page and site.
So for a given input test sequence a user can come up with, there must be expected values or outcomes from the site that WebUI can test for with Verifications and Wait For test steps.
You can also data drive this same test sequence, the inputs and verifications, as described in the 'Creating a Data Driven Test' topic for Dev
quick start guide to a data source.
If you wanted to, you can just create data driven verifications also. Please let us know if you have any further questions for this.
All the best,
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items