Testing Power Apps custom pages

Build a custom-page workflow in a normal test case and run it in Background. The case's Execution persona is used for the workflow, just as it is for other steps. If no persona is selected, the connection's saved session is used.

1. Start with Open environment and, if needed, Open app.
2. Add Open custom page from Navigation. Enter the page's logical Name from your solution, for example cr123_requestpage. This opens it inline in the current model-driven app using Microsoft's custom-page navigation API.
3. Add Set field value. Field steps added after Open custom page default to typed labels rather than Dataverse metadata. Use the control's accessible label or placeholder, for example Request title, and enter the test value. Add more fields as needed.
4. Add Click button, with Submit or your button's exact accessible name.
5. Add Verify message/text for the expected success message, or an appropriate Verify Dataverse record step to check the saved data. Clicking Submit alone does not prove the submission succeeded.
6. Save and run the suite in Background, then review its shared logs and reports.

This first version supports inline custom pages, text inputs, text areas, native dropdowns, and dropdowns exposing accessible combobox/option roles. It addresses visible controls inside embedded frames, including cross-origin frames. Accessible labels must be unique; ambiguous targets, disabled buttons, read-only fields, and navigation errors fail the step.

For existing field steps, enable Use text fallback for this step under Advanced settings and type the label. Canvas control names and Dataverse column names are not substitutes for accessible labels. Custom controls that do not expose these accessible roles need additional support. Custom-page dialogs, record-context parameters, and Browser extension execution are not part of this first version. No AI model is needed to execute these steps.