Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

UI test steps

Log in to subscribe to topics and get notified when content changes.

UI test steps

Test user interfaces by mimicking user actions and interacting with the visible components of a page.

Client test runner dependency

UI test steps require an active client test runner to act directly on the visible components of a page. A tester must manually start one or more client test runners for UI testing. Test designers can schedule selecting an open client test runner from a test suite. See Working with client test runners.

Intelligent wait mechanism

UI test steps have an intelligent wait mechanism triggered by UI changes such as clicking a component or setting a value. The wait mechanism requires the UI change to complete before the next UI test step can proceed. Test designers do not need to manually add wait mechanisms between UI test steps.