Testgrity user guide

Testgrity helps you create, organise, run, and review automated tests for Microsoft Power Platform and Dynamics 365 model-driven apps.

Last updated: 2026-10-05

Guide contents

1. Getting started — sign in, set up and manage your workspace, invite users, choose a project, manage your profile, connect an environment, and submit an issue or feedback.
2. Designing tests — create suites and cases, retrieve metadata, and build test steps.
3. Recording tests — capture a D365 workflow with the browser recorder.
4. Running tests and reviewing reports — run a suite, monitor progress, cancel a run, and inspect evidence.
5. Action reference — a quick reference to actions available in the Designer and supported in recorded or existing cases.
6. Browser support and getting help — recommended browsers and screen size, current limitations, and how to report a problem.
7. Troubleshooting — solutions for common connection, recording, execution, and report issues.
8. Access regression testing — create access cases in Designer and run persona checks, review effective rights, and use optional AI assistance.
9. Testing custom pages — open a Power Apps custom page, fill fields, submit, and verify the outcome in a normal case.

Typical workflow

1. Sign in and complete any required legal or workspace setup. Testgrity restores your last open project.
2. Add a Dynamics 365 environment and connect it for Background execution.
3. Retrieve the environment's Dataverse metadata.
4. Create a suite and add test cases with the Designer or recorder.
5. Select Run, choose a suite and execution mode, and start the run.
6. Expand the suite log and open each case report to review steps and artifacts.

Recently added

• Access testing preview — review expected record rights across personas, publish background checks, compare compatible results, and optionally draft or explain with Azure AI Foundry.

• Clearer connection status — distinguish the Selected connection from Connected/Disconnected sign-in status, with red status text and badges when reconnection is needed.

• Organisation workspaces — name a workspace during registration, review its ID and members, and let the owner update its name.

• Workspace invitations — invite members or administrators by email, retry delivery, copy the saved invitation link, and revoke pending invitations.

• Persistent project selection — switch projects from the header and automatically reopen the last project used by your account.

• Project creation dialog — create a project in a focused popup without separate project access levels.

• Workspace API tokens — trigger suites from GitHub Actions or Azure DevOps, review creator and usage details, and revoke credentials.

• Clearer navigation — use the Designer and Run icons to move between authoring and execution.

• Visible empty suites — keep suites in the project list even before their first case is added.

• Report discovery and insights — search and filter server-side suite history, review pass-rate trends, outcome composition, and recurring failures.

• Portable reporting — export CSV or JSON, download a complete evidence ZIP, or print an executive run summary.

• Scheduled report email — deliver the latest completed suite run daily or weekly to configured recipients.

• Scheduled suite runs — run suites once, daily, or weekly in the background with timezone-aware history and failure notifications.

Application releases are promoted by administrators through TEST, UAT, and PROD. A normal application update does not require you to recreate projects, connections, suites, cases, or reports.

Screenshots in this guide are illustrative. Names, counts, available controls, and execution options may differ by deployment. Environment URLs are sanitised.