--- sourceDocument: Zurich Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/application-development Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Page Inspector # Page Inspector {#ariaid-title1} * Release version: Zurich * * Updated July 31, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Page Inspector Release version: Zurich The Page Inspector is a developer tool within the ServiceNow AI Platform that facilitates the identification and testing of HTML and JavaScript components in user interfaces. It enhances automated testing by ensuring that only testable components are included in your UI elements. Show full answer Show less ## Key Features * A highlighted frame showing the currently inspected page. * A toggle icon to display or hide the Inspector pane. * A refresh button for updating the list of page components. * A search filter for page components. * An inspector button to pinpoint specific components. * Information preview and detailed attributes for selected components. * Label Path field for hierarchical context around elements. ## Testable and Untestable Components The Page Inspector categorizes components into testable and untestable. Testable components are standard HTML and JavaScript accessible to the Automated Test Framework for custom UI testing. Untestable components include: * **Exclusion listed:** These components cannot be tested using Custom UI steps and typically include specialized UIs or components testable by other means. * **Inaccessible:** Elements the Automated Test Framework cannot identify due to permission issues or configuration problems, often third-party libraries or Shadow DOM elements. To test exclusion listed components, alternate test categories such as Forms or Service Catalog must be used. ## Inspect Different Page Types Utilize the Page Inspector to examine and troubleshoot various page types, including UI Pages, Service Portal, Standard UI, and Custom URL pages, ensuring comprehensive testing across your ServiceNow environment. Identify the HTML and JavaScript page components in your user interfaces that are available for custom UI testing. Enable automated testing by ensuring that your user interfaces only contain testable page components. The Page Inspector is a developer setting that opens a new pane beside any currently displayed ServiceNow AI Platform page. The Page Inspector provides these features. 1. A highlighted frame to identify the currently inspected page. 2. A banner icon to display or hide the Inspector pane. 3. A button to refresh the list of page components. 4. A button to hide the Inspector pane. 5. An inspector button to identify specific components on a page. 6. A list of page components available for custom UI testing. 7. A page component search filter. 8. A row to click to see more information about a page component. 9. A highlighted row and tooltip to preview information about the currently inspected component. 10. A highlighted page component to identify the currently inspected component on the page. 11. A component label and back button to return to the list of page components. 12. A list of actions to take on the current page component. 13. A list of attribute information for the current page component. 14. An attribute name and value pair for a page component. Note: You can use the Label Path field to show the hierarchical page context around an element while inspecting a component on a page. If there are many "ancestor" label paths of an element, it can display only three. Each label path element is separated by a \>. It can be used to differentiate between two similar looking components. {#atf-page-inspector__ul_qg2_n1j_qfb} Note: UI buttons with icons are now visible in the page inspector. ## Page inspector launcher {#atf-page-inspector__section_szl_lpb_blb} The page inspector launcher helps you select and launch a specific page within the page inspector. See [Inspect different page types](https://www.servicenow.com/docs/6NOtqVWQ4NZa6vvQmr6BZw "Inspect and troubleshoot the functionality of different page types like UI Pages, Service Portal, Standard UI, and Custom URL using the Page Inspector.") for more information. ## Testable page components {#atf-page-inspector__section_wj4_hyj_qfb} The Page Inspector retrieves the list of testable page components when you first load a page. Testable components consist of standard HTML and JavaScript that are accessible to the Automated Test Framework. Test designers can use these components as part of custom UI testing. ## Untestable page components {#atf-page-inspector__section_bwv_zrw_qfb} The Page Inspector identifies these types of untestable page components. Exclusion listed : Exclusion listed page components can't be tested using any Custom UI test steps. Exclusion listed page components typically include specialized ServiceNow AI Platform user interfaces and components already testable by other means. Test designers can't create custom UI tests for exclusion listed page components. To test these components, they must use another supported test category such as Forms or Service Catalog. In the Page Inspector, the exclusion listed interfaces are indicated by a grey background color when the inspect icon is dragged over them. A detailed message about the step category that needs to be used to test these components is displayed by dropping the inspect icon on an exclusion listed component. * Lists can't be tested using custom UI test steps. Use [List and Related List](https://www.servicenow.com/docs/lqW21y4off5vOd9YF8AqFw#test-steps-list-related-list "Validate the functionality and visibility of records and UI actions in lists and related lists.") test step category to test lists.Figure 1. Sample exclusion listed list message * Forms can't be tested using custom UI test steps. To test forms, use [Form category](https://www.servicenow.com/docs/BdLFbx6EsgIQSzi5NVh_XQ#test-steps-form-category "Validate the functionality of fields and UI actions on a form.") test steps.Figure 2. Sample exclusion listed form message Note: The UI formatters within forms can be accessed and tested using custom UI test steps. See [Create a custom UI test](https://www.servicenow.com/docs/j0a0MkJYhmL2P48kS93gMA "Test components in custom UI pages.") for more information. * Service Catalog items can't be tested using custom UI test steps. To test catalog items, use [Service Catalog category](https://www.servicenow.com/docs/hPGNO6OZU4gOUDh9shx1Hg#test-steps-service-catalog-category "Validate single catalog item transactions as well as requester and fulfiller flows in Service Catalog.") test steps.Figure 3. Sample exclusion listed catalog item message * Certain components are excluded from custom UI pages and are forbidden from being tested.Figure 4. Sample exclusion listed component message * Workspaces can't be tested using custom UI test steps. To test forms in an available workspace, use [Form category](https://www.servicenow.com/docs/BdLFbx6EsgIQSzi5NVh_XQ#test-steps-form-category "Validate the functionality of fields and UI actions on a form.") test steps.Figure 5. Sample exclusion listed workspace message {#atf-page-inspector__ul_sd5_3vw_sjb} Inaccessible : Inaccessible page components are elements that Automated Test Framework either cannot identify or does not have permission to test because of some configuration issue. Inaccessible page components typically include third-party JavaScript libraries or elements with a Shadow DOM. Test designers cannot create custom UI tests for inaccessible page components, but may be able to redesign the page to use components accessible to Automated Test Framework. * Certain components are not accessible in the Automated Test Framework Figure 6. Sample inaccessible component message * Team development is not supported in the Automated Test Framework Figure 7. Sample unsupported component message * Testing external sites that are embedded in platform pages is not supported in the Automated Test Framework Figure 8. Sample unsupported embedded external sites message {#atf-page-inspector__ul_ax2_xyw_sjb} * **[Inspect different page types](https://www.servicenow.com/docs/6NOtqVWQ4NZa6vvQmr6BZw)** Inspect and troubleshoot the functionality of different page types like UI Pages, Service Portal, Standard UI, and Custom URL using the Page Inspector.