Automation is only the starting point of testing where the browser is manipulated automatically without tester intervention. Once you've automated the interaction, you still have to test something, such as measuring and recording that an occurrence happened or did not happen as expected. There are several ways to verify elements in Test Studio:

Progress Telerik TestStudio Dev  image
New to Progress Telerik TestStudio Dev?

Progress Telerik TestStudio Dev is a To try it out sign up for a free 30-day trial.

  • Quick Verification - create an easy verification from the Quick Step menu when an element is highlighted.

  • Advanced Verification - craft a custom verification from the Sentence Verification Builder.

  • Wait - pause the test execution until the comparison is true.

  • Extraction - extract an element's value and reuse it later in your test.

  • Image Verification - this feature is based on an element’s visual rendering rather than the properties or attributes of that element.

Verifications in Test Studio allow you to:

  • Measure against multiple criteria at one time.
  • Build these measurements in an interactive manner without code.
  • Detect if elements are in a particular state (e.g. is visible, exists).
  • Detect if attributes and properties compare with specific values.
  • Verify content, attributes, styles, visibility, drop-down list selections, checkboxes, radio buttons, tables and Silverlight property values.

Test Studio Dev implements verification through "sentences" that compare a portion of an element to a value, such as:

  • textbox content is equal to 'order 2011'
  • image path contains ''
  • wait for element to exist

Test Studio cannot read and verify against the contents of a PDF file loaded in the browser, as it does not have a DOM structure like a traditional web page. If you can store that information in a file type such as XLS, XML, CSV, or a SQL database, then you can use the Data Driving feature.

In this article
Not finding the help you need? Improve this article