Troubleshooting

Back to the guide index

Run suite is disabled

Confirm that:

• A suite is selected.
• The suite contains at least one test case.
• An environment is selected.
• For Local, Background, or Docker execution, the environment is connected.
• For Browser, the environment has a D365 URL and the Testgrity Recorder extension is installed, enabled, and detected.
• No other suite is currently queued or running for your user.

Reconnect the environment if its saved session has expired or its status indicates that attention is required.

Browser execution is unavailable

The Browser option appears only when browser-extension execution is enabled for the deployment. If it appears disabled:

1. Install or update the Testgrity Recorder extension using the instructions in Recording tests.
2. Confirm that the extension is enabled in the same Chrome or Edge profile as Testgrity.
3. Refresh Testgrity so it can detect the extension.
4. Confirm that the active environment has a Dynamics 365 organisation or app URL.

Contact the administrator if the option does not appear at all.

A browser run does not start or stops early

• Allow the extension to open the D365 test tab, and keep it open until the run finishes.
• Confirm that D365 is signed in within the same browser profile.
• Do not close or navigate away from the test tab while the suite is running.
• If a step reports that an action is not supported by Browser execution, run the suite with Local, Background, or Docker execution instead.
• Browser runs do not produce Playwright videos or traces; use the step results and error text when diagnosing them.

The suite stays queued

Queued runs require an available execution worker. If the status does not change, contact the administrator and provide the suite name, environment name, and approximate queue time.

D365 asks for sign-in during a run

Reconnect the active environment to renew its saved session. Some tenants require MFA or Conditional Access interaction. A local headed runner may leave the browser open so you can complete that prompt; a headless worker may require the connection to be refreshed beforehand.

Metadata is unavailable or outdated

1. Confirm the intended environment is active.
2. Reconnect it if needed.
3. Select Retrieve metadata or Refresh model.
4. Open the metadata settings and confirm the needed entity is included.

Metadata reflects the selected environment. Published D365 customisations may need time to become available.

If refreshing continues to return a stale or unusable model, select the trash button beside Refresh model, confirm removal, and then select Retrieve metadata. Removing the cache temporarily switches supported steps to text fallback but does not delete saved tests or the environment connection.

Start Recording is disabled

Confirm that an environment is selected. If the recorder workspace asks for an extension, install it, refresh Testgrity, and select Check Extension. In hosted deployments, recording also requires the browser extension or a configured remote recorder.

Recording produces no events

• Confirm the recorder reports Recording before interacting with D365.
• With the extension, use the D365 tab in the same browser profile as Testgrity.
• Refresh the D365 page after installing or updating the extension.
• Stop and reset the session, then begin a new recording.

An action cannot find a target

• Check spelling if the step uses typed text.
• Refresh metadata and reselect the target.
• Confirm the correct app and area are open before table or command actions.
• Add Wait for form ready or Wait for grid load after navigation.
• Use the report screenshot, video, or trace to see the UI state at failure time.

A negative test fails unexpectedly

Open the full case report and inspect each step's Expected and Actual values. A step set to expected failure fails the test if the action succeeds. It also may fail for the wrong reason, so verify that the reported error represents the business rule being tested rather than a missing target, timeout, or authentication problem.

An artifact is unavailable

Screenshots, video, diagnostic traces, and detailed execution reports depend on workspace settings, retention policy, deployment configuration, and the runner that executed the test. If screenshot capture, video recording, or trace generation was switched off before the run, the related button is not shown in the report. A report can still contain step status and error information even when an artifact was not produced or has expired.

Browser runs do not currently create Playwright videos or traces, even when those workspace settings are enabled.

Report an issue is unavailable

The Report an issue button appears only when issue reporting is enabled for the deployment and you are authenticated. If the button is visible but the dialog reports missing GitHub credentials, contact the administrator. If a submission fails, try again after a few minutes and make sure screenshots are PNG, JPEG, or WebP files no larger than 5 MB each and 10 MB in total.

When escalating a problem, include the project, suite, case, environment, run date, result status, and the relevant error text. Do not send passwords or saved authentication files.