Getting started

Back to the guide index

Sign in

Open the Testgrity URL supplied by your administrator. If authentication is enabled, select Sign in and complete the Microsoft customer account sign-in or registration process. Select Read the User Manual if you need guidance before signing in.

During registration, you may be asked to provide your name, company, and job title. You must also accept the Testgrity Terms and Conditions and Privacy Policy and acknowledge that Testgrity is a private beta. Registration creates an account but does not grant workspace access. A Testgrity administrator must approve the account, and Testgrity sends an email when access is ready. Automated tests can change or delete data in a connected environment, so use an appropriate test environment and test data.

After registration and legal acceptance, an account that has not yet been approved opens Beta access pending. You can review the legal documents or contact support from that page. When the approval email arrives, sign out and sign in again so Microsoft can issue a fresh identity token containing the beta access role.

If the current legal documents have not been accepted for your account, Testgrity opens Legal acceptance before the workspace. Review the linked documents in a new tab, select both required checkboxes, and select Accept and continue. You may be asked to accept again when the documents change. If an existing session predates legal acceptance tracking, follow the prompt to sign out and sign in again first.

After sign-in, the header provides:

• Designer — create and maintain suites and test cases.
• Run — execute suites and review suite logs.
• Connection — choose the environment used by test runs.
• Profile — edit your identity, switch projects, configure run evidence, open the User Manual, delete your account, or log out.

Manage your profile

1. Open the profile menu in the upper-right corner.
2. Select Profile.
3. Update your first name, last name, company, or job title/description.
4. Select Save profile.

First name and last name are required. Company and job title are optional. When Microsoft Entra profile editing is configured, these values are saved in Testgrity and synchronised to your Microsoft Entra profile. The profile also shows your Testgrity user ID and workspace ID, which can help when requesting support.

If the fields are read-only, Microsoft Entra profile editing is not configured for the deployment. Contact your administrator if the identity details are incorrect.

Delete your account

Account deletion is permanent for Testgrity data:

1. Open the profile menu and select Profile.
2. Select Delete account.
3. Review the deletion summary.
4. Select Delete account permanently.

Testgrity deletes your profile and any workspace that you solely own, including its projects, tests, environments, results, saved authentication state, and stored run artifacts. Shared workspaces remain available to their other members.

Your Microsoft Entra identity is also deleted and can no longer sign in. An Entra administrator may be able to restore that identity for up to 30 days, but the deleted Testgrity data is not restored with it.

Account deletion is blocked while a test run in an affected workspace is queued or running. Cancel the run or wait for it to finish, then try again. If Testgrity asks you to sign in again or reports that account deletion is not configured, follow the prompt or contact your administrator.

Select or create a project

A project separates its suites, cases, environments, and results from other work.

1. Open the profile menu in the upper-right corner.
2. Select Projects.
3. Select an existing project, or enter a name and optional description under New Project and create it.

The selected project remains active in the browser. A project can be deleted only when it is not the default project and contains no suites or environments.

Add an environment connection

1. In the header's Connection panel, select +.
2. Select the project that owns the connection.
3. Enter a display name and select the application type. Model-driven app is currently available; Canvas app and Power Pages site are shown as coming soon.
4. Choose an authentication method:
   • Interactive browser sign-in is recommended for MFA, passwordless sign-in, and Conditional Access. Enter the organisation URL, select Connect, and complete sign-in in the Chrome or Edge tab opened by the extension. Testgrity encrypts the captured D365 session for Browser or Background execution until Microsoft requires interactive authentication again; your password is not captured.
   • Unattended automation account uses a dedicated test account without MFA. Enter the organisation URL, username, and password, then select Connect. Signs in automatically and creates an encrypted reusable session, so tests can run in the background.

Interactive connections use the extension to retrieve Dataverse apps, metadata, and choice values through the signed-in browser profile. When you save or reconnect an interactive environment, Testgrity automatically refreshes the metadata model in the background. Their encrypted session can also be used for Background execution. If Microsoft requires sign-in, MFA, or Conditional Access again, Testgrity stops the run and marks the connection as expired until it is reconnected in the browser. If the extension is not detected, Interactive browser sign-in is disabled and the connection dialog provides the extension download and installation instructions.

For unattended connections, the password is used only while connecting and is not saved. Testgrity saves an encrypted reusable browser session for Background execution.

The closed selector and each item in the connection list show an authentication-method badge beside the environment name: Interactive · MFA (blue) or Unattended (purple). Connection readiness remains separate. The selector list labels connections Active or Inactive, while the top of the Connection panel provides the more specific status.

When a saved session exists, the detail below the selector reads Authenticated followed by the authentication date and time. If the session has a known expiry, it also shows Expires followed by the expiry date and time. The connection type is omitted from this detail because it is already visible in the badge.

Connection status can be:

• Active — the saved session is ready to use.
• Needs reconnect — the saved session has expired; connect again before running tests.
• Not set — no reusable session is currently available.

Use the plug button to connect an environment that has no saved session or to reconnect an expired session. When the selected connection is active, the red trash button deletes it after confirmation. The current portal does not provide a separate edit command for an active connection; create a replacement connection if its saved configuration must change.

Retrieve Dataverse metadata

Metadata powers the app, entity, field, and option selectors in test steps.

1. Open Designer and select or create a test case.
2. Confirm the correct environment is active.
3. In the Metadata panel, select Retrieve metadata.
4. Wait for the progress indicator to finish.
5. Optionally use the settings icon to choose which entities are included in selectors. Search for an entity, select or clear individual entities, or use Select all and Clear all. Changes are saved automatically when you close the entity selector.

Use Refresh model after relevant Dataverse customisations are published. The panel shows the number of selected and available entities and fields, the source environment, and when the model was last loaded.

To discard the cached model, select the trash button beside Refresh model and confirm the removal. This clears the cached metadata for the active environment and switches supported steps to text fallback. Select Retrieve metadata to load the model again.

During an application update

Testgrity administrators promote a tested application release through TEST, UAT, and PROD. The application may restart briefly while the approved release is applied.

• Avoid starting a long suite during a communicated maintenance window.
• A normal application deployment preserves projects, environment connections, suites, cases, run history, and retained artifacts.
• If Testgrity was open during the update, refresh the browser after the administrator confirms that deployment is complete.
• If a page continues to show an error after refreshing, use Report or contact the administrator with the environment name and approximate time.

Report an issue or provide feedback

If reporting is enabled for your deployment, a floating Report button appears in the lower-right corner of authenticated pages.

1. Select Report.
2. Choose Report an issue or Provide feedback.
3. Enter a short title and description. For an issue, explain what happened, what you expected, and how to reproduce it. For feedback, describe what works well, what could be improved, or what you would like to see.
4. Optionally paste, drag and drop, or choose up to three PNG, JPEG, or WebP screenshots.
5. Review every screenshot and remove credentials, customer data, and other sensitive information.
6. Select Create.

Each screenshot must be 5 MB or smaller, and all screenshots together must be 10 MB or smaller. After submission, Testgrity confirms whether the issue report or feedback was submitted, shows the GitHub issue number, and provides a View on GitHub link.

The button is hidden when reporting is disabled. If it is enabled but the GitHub connection is incomplete, the dialog explains that setup is required; contact your administrator.

Next step

Continue to Designing tests.