New in TestGrid: TOTP Automation, Cross-Suite Reuse, and Clearer Failures

As your test library grows, the work around execution grows with it. You have more test cases to maintain, more shared functions to manage, more execution history to interpret, and more dependencies across tools and teams.

TestGrid’s latest updates focus on those everyday testing workflows.

You can now reuse functions across suites, make bulk test-case changes faster, trace executions with more context, investigate failures earlier, and include accessibility checks within real-device testing.

Let’s see what has changed.

TL;DR

• TestGrid Authenticator brings TOTP-based 2FA into automated login flows, while qTest enhancements improve Test Suite management, runner attribution, synchronization visibility, and execution traceability.
• Test case editing is faster, with multi-step selection in Test Case Explorer and CoTester Studio reducing repetitive changes across longer tests.
• Common test functions can now be reused across multiple suites within the same version, cutting duplicate automation logic and simplifying maintenance.
• Admins get more visibility into shared test assets, with dashboard notifications when test cases or test functions are marked for deletion.
• Execution history is easier to trace, with test-version information available directly in logs and build steps.
• Scriptless failures are easier to investigate, with primary failure categories surfacing the likely cause before teams dig into detailed logs.
• Mobile accessibility testing now fits into real-device workflows, with severity, WCAG criteria, screenshots, suggested fixes, and Jira tracking available as part of the testing process.

1. Enterprise Authentication and Test Management

Enterprise testing often depends on more than the test itself. Authentication steps need to work reliably, and test-management systems need to carry enough context to make execution easier to follow. These updates address both areas:

a. TestGrid Authenticator for TOTP-based 2FA

Two-factor authentication can interrupt an otherwise automated login flow when a test reaches the step that requires a time-based verification code.

TestGrid Authenticator supports TOTP-based 2FA by allowing the TOTP secret/setup key to be securely configured once. TestGrid can then generate the verification code during automated execution.

This enables flows such as Login → 2FA Verification Code → Application Access → Continue Test to remain part of the automated journey instead of requiring someone to open an external authenticator and enter the code manually during each run. 

Applications using TOTP-based authentication, including services such as Salesforce, GitHub, Google Accounts, and Microsoft Accounts, can use this type of flow.

Also Read: How to Test Multi-Factor Authentication?

b. Enhanced qTest integration

You can now manage Test Suites at the version level. The Run By field now shows the actual build runner, while synchronization status and execution traceability make it easier to follow activity between TestGrid and qTest.

These enhancements provide better visibility into which runner executed a build, whether synchronization completed successfully, and how executions map between TestGrid and qTest.

2. Easier Test Creation, Reuse, and Governance

Larger automation libraries create more maintenance. Repeated edits take longer, duplicate workflows become harder to keep consistent, and changes to shared assets can affect multiple users. The following capabilities minimize some of that overhead:

a. Faster test case editing

Test Case Explorer and CoTester Studio now include Select All functionality.

You can select and manage multiple test steps together instead of editing them one at a time. This is especially useful in longer test cases when the same change needs to be applied across several steps.

b. Cross-suite test functions

Workflows such as Login, Data Setup, or Logout often appear across several test suites. Recreating them in each suite leaves you with multiple versions of the same automation logic to maintain.

You can now reuse a common test function across multiple test suites within the same version. Once the function exists, you can call it wherever that workflow is required.

That reduces duplicated logic and the number of workflow copies that need maintenance when a shared process changes.

c. Dashboard notifications for test case and test function deletions

Deleting a shared test case or test function can affect other users working within the same project or test library.

Company, Cloud, and Team Admins now receive dashboard notifications when these assets are deleted. The deletion process also includes an additional checkpoint: the asset is first marked for deletion and is removed after Commit & Sync.

This provides teams with an additional review point before shared automation assets are permanently removed.

Also Read: What’s New at TestGrid – Broader Coverage, Faster Execution, Tighter Control

3. Clearer Execution and Faster Failure Investigation

When an execution fails, the first useful question is often simple: what exactly ran, and what kind of failure occurred? Two recent updates make that information available earlier in the investigation:

a. Test version visibility in execution logs

Test cases change over time, so execution history becomes harder to interpret when the version that ran is unclear. You can now see test-version information directly in TestGrid’s execution logs and build steps.

When you are troubleshooting a failure, reviewing a historical run, or comparing results after a test has changed, you can trace the execution back to the relevant version. That reduces ambiguity when different versions of the same test case have produced different results.

b. Failure categories in Scriptless execution

A failed result tells you that something went wrong. The next task is identifying where to start looking. Scriptless Execution now surfaces a primary failure category alongside the failed result across the Dashboard, Build Details, Logs, and Troubleshooting views.

Categories include Element Not Interactable, No Locator Found, Assertion Failed, App Crash, Data Error, Compile Failure, Device Lost, and infrastructure-related failures.

You can use the category to narrow the first stage of troubleshooting before moving into the relevant logs or diagnostic information.

4. Mobile Accessibility Testing

Accessibility issues are easier to address when they are identified during the same testing process you already use for mobile applications.

TestGrid now brings mobile accessibility testing into the Real Device Cloud workflow for Android and iOS applications.

While testing a screen on a real device, you can generate a report showing detected accessibility issues, severity, affected WCAG criteria, screenshots, and suggested fixes. Findings can also be tracked through Jira when needed.

This allows mobile accessibility checks to become part of broader QA rather than a separate testing activity. You can see where an issue appears, understand the relevant accessibility requirement, and log the findings in the existing defect-tracking process.

More Context Across the Testing Workflow

At TestGrid, we’re continuing to refine the platform around the work that happens before, during, and after test execution. This month’s updates add more control over how tests are created and managed, while making execution results easier to understand and act on.

We’ll continue introducing improvements across these workflows as the platform evolves. If you want to see how the latest capabilities fit your current testing setup, request a free TestGrid trial and explore them with our team.