TestgrityBack to portal

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 organisation's sign-in process. Select Read the User Manual if you need guidance before signing in.

Testgrity sign-in page

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 — view your identity, switch projects, configure run evidence, open the User Manual, or log out.

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 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.

New environment connection dialog

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 by local, Docker, or Azure background workers. 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 local, Docker, or Azure background workers.

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 a separate status, shown at the right of each list item and at the top of the Connection panel.

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 or reconnect. Use the red disconnect button to delete the selected connection. To edit the selected connection, open its connection settings from the selector.

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 limit the entities included in selectors.

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.

Report an issue

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

  1. Select Report an issue.
  2. Enter a short title and describe what happened, what you expected, and how to reproduce it.
  3. Optionally paste, drag and drop, or choose up to three PNG, JPEG, or WebP screenshots.
  4. Review every screenshot and remove credentials, customer data, and other sensitive information.
  5. Select Create GitHub Issue.

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

The button is hidden when issue 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.