---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# UI test steps

# UI test steps {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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

## Client test runner dependency {#ui-test-steps__section_ckg_xf2_tfb}

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](https://servicenow-prod.fluidtopics.net/RCkgkemnippD_sUkq2mTnw "If an automated test includes steps that involve a form or any other user-interface (UI) element, it runs those steps in a browser tab or window called a test runner or client test runner.").

## Intelligent wait mechanism {#ui-test-steps__section_ewk_x3l_1gb}

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.
* **[Custom UI test steps](https://servicenow-prod.fluidtopics.net/kwiNPNHTqgSJzUcwnNTeeg)**   
  Test customized user interfaces such as UI pages and UI macros by retrieving their HTML and JavaScript page components and identifying the test actions they support.
* **[Browser recommendations for Automated Test Framework](https://servicenow-prod.fluidtopics.net/tu4HB4Dg09eF~AVKNNIb0g)**   
  Configure client test runner browsers to run automated tests and avoid performance degradations.
* **[Working with client test runners](https://servicenow-prod.fluidtopics.net/RCkgkemnippD_sUkq2mTnw)**   
  If an automated test includes steps that involve a form or any other user-interface (UI) element, it runs those steps in a browser tab or window called a test runner or client test runner.
* **[Pick a browser](https://servicenow-prod.fluidtopics.net/MowfYHt0cQxkNUHtEOESRQ)**   
  If the test or test suite you are running contains steps that work with a form (any step involving a UI), or any other UI test step element (such as Automated Service Catalog test steps), work with the Pick a Browser dialog.