Skip to main content

Manage Test ID access with an access group role (8.2)

Suggest edit Updated on May 3, 2021

Test IDs allow Pega application developers to create a unique identifier for each user interface component. Test IDs are unique numerical strings that appear in the markup of an application. An automated test can use the test ID to identify a user interface element and run a test against it.

Access to the test ID functionality is controlled by a role within an access group. Not all Pega Platform™ users require access to the test ID functionality. Only developers who create or run tests against the UI need access to the test ID functionality. Limiting access prevents accidental alteration of the test IDs. At run time, without the test IDs included in the code, the client downloads less code, improving performance.

Access to test ID functionality is controlled by the PegaRULES:TestID role. By default, access groups do not include the PegaRULES:TestID role. You can grant access to the test ID functionality by adding this role to an access group.

  1. In Dev Studio, create a new access group or open an existing access group that you want to grant access to the test ID functionality by clicking Records > Security > Access group. Select the access group from the list.
  2. On the Definition tab in the Available roles section, click Add Role.
  3. In the blank text area added to the end of the Available roles list, enter PegaRULES:TestID.
    Thumbnail
    The Access group with the PegaRULES:TestID access role.
  4. Save the access group.

Members of the access group now have access to the test ID functionality. To add a test ID to a user interface element, open the General tab of the properties panel in and click the Generate ID button. For more information on user interface elements that support the test ID functionality, see Test ID and Tour ID for unique identification of UI elements.

Thumbnail
The General tab of the Properties panel showing the Test ID
  • Previous topic Improve user experience and enable native search in mobile apps with UI-Kit 14 (8.3)
  • Next topic Improve design consistency with UI-Kit 13 (8.2)
Did you find this content helpful? YesNo

75% found this useful

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us