Choose which optional cookies you allow. Essential cookies are always on. Your choice lasts for six months and applies to the Testgrity website and workspace.

Essential

Sign-in, security, and remembering your cookie choices.

Always on

Cookie and privacy policy. You can change or withdraw consent at any time using Cookie settings.

TestgrityBack to portal

Browser support and getting help

This page explains which browsers work best with Testgrity, the current private-beta limitations, and what to include when you ask for help.

Recommended browser and screen size

Use the latest desktop version of one of these browsers:

  • Google Chrome on Windows or macOS.
  • Microsoft Edge on Windows or macOS.

Keep browser zoom at 100%. The browser window should be at least 1280 × 720 pixels. A size of 1440 × 900 or larger gives the Designer, run details, and reports more room.

Chrome or Edge is required when you:

  • sign in to a Dynamics 365 environment through your browser;
  • record a test with the Testgrity Recorder extension; or
  • run a suite in Browser mode.

Keep both the Testgrity tab and the Dynamics 365 tab open until the recording or run finishes. Allow the Recorder extension to open the Dynamics 365 website configured for the connection.

Firefox, Safari, phones, tablets, private or incognito windows, and smaller browser windows are not currently supported during the private beta. Some pages may open, but recording and test execution may not work correctly.

Current limitations

  • Browser runs happen one case at a time. Keep the Dynamics 365 tab open until the suite finishes.
  • Video recording needs your permission. When prompted at the start of a Browser run, select the Testgrity extension button to allow tab recording.
  • Some advanced actions are not available in Browser mode. If a case uses one, the step stops and explains which action is unsupported. Testgrity does not automatically switch to another execution method.
  • Background runs need a saved Dynamics 365 sign-in. Microsoft may ask you to sign in again after MFA, a password change, a security-policy change, or session expiry. Reconnect the environment before running the suite again.
  • Parallel execution may affect shared test data. When your deployment allows multiple cases to run together, use separate records and accounts so one case does not change data needed by another.
  • Metadata can become out of date. Refresh the environment metadata after apps, tables, fields, forms, or choices change in Dynamics 365.
  • Evidence may contain business or personal data. Review your workspace screenshot, video, trace, and retention settings before running tests with sensitive information.
  • The service is still in private beta. Features may change, and uninterrupted availability or a specific support response time cannot be guaranteed.

Report a problem

When the Report button is available in Testgrity:

  1. Select Report.
  2. Choose Report an issue.
  3. Explain what you were doing, what you expected, and what happened.
  4. Attach a screenshot only after removing confidential or personal information.
  5. Select Create.

If the Report button is unavailable, email contact@dynamicsduo.com.au.

Include as much of the following information as you can:

  • the Testgrity page where the problem happened;
  • the approximate date and time, including your time zone;
  • the workspace, project, environment, suite, and case names involved;
  • the visible run ID or case number, if available;
  • whether you used Chrome or Edge;
  • whether you selected Background or Browser execution;
  • what you expected to happen;
  • what happened instead; and
  • the shortest set of steps that reproduces the problem.

Do not send passwords, session cookies, API tokens, unredacted customer data, or confidential Dynamics 365 records.

Urgent problems

Treat a problem as urgent if it may involve:

  • exposed customer or personal data;
  • unexpected deletion or damage to Dynamics 365 data;
  • a security concern; or
  • Testgrity being completely unavailable.

Stop the affected run or disconnect the affected environment when it is safe to do so. Put URGENT BETA INCIDENT in the report title or email subject so the team can identify it quickly.

What happens after you report an issue

The support team will review the information and prioritise problems involving security, privacy, data loss, or a complete service outage.

Whenever possible, the team will reproduce the problem, prepare the fix, and validate it in internal environments before updating the live Testgrity service. The team will share any available workaround and confirm the outcome or explain a known limitation.

Support during the private beta is provided on a best-effort basis unless a separate written support agreement applies.