
TestGrid Release Notes
Check out the latest feature releases, enhancements and platform updates.

Check out the latest feature releases, enhancements and platform updates.
March 14, 2026
Introduced a robust tag-based filtering mechanism within the Scriptless Writer dashboard, allowing you to isolate specific test suites quickly. This update combines seamlessly with our current text-search patterns to provide highly granular control over your test repositories.
Multi-Tag Filtering Mechanics: Added comprehensive support to sort test inventories using single or multiple intersecting tags, ensuring accurate retrieval of matching cases.
Unified Search Integration: Combined the new tag filters directly with our traditional keyword search fields, allowing teams to query by specific text strings, distinct tag attributes, or both parameters simultaneously.
State and Pagination Controls: Optimised background pagination logic to ensure that your active multi-tag filters remain securely locked in place during page navigation or view refreshes.
Scriptless UI Adjustments: Enhanced the primary Scriptless Writer console with intuitive tag selection fields, backing the interface with updated conditional logic to handle complex search queries efficiently.
As test case repositories expand into hundreds or thousands of workflows, finding specific scenarios via text keywords alone can become time-consuming. By adding structured multi-tag filtering directly into your workspace, testing teams can instantly narrow down their view to specific modules, target environments, or sprint milestones—drastically accelerating script maintenance and execution setup.
March 14, 2026
Upgraded core hardware tracking infrastructure to recognize, isolate, and accurately report on reserved device assets. This ensures that session coordinators and provisioning workflows interact with exact, real-time availability metrics.
Explicit Reserved State Identification: Enhanced the internal device manager to track hardware set aside for specific tasks, distinguishing these assets clearly from general-availability pools.
DeviceInfo Payload Standardization: Upgraded the primary device telemetry endpoint to return clear reservation parameters, ensuring downstream tooling can immediately identify a resource's exact assignment state.
Guaranteed Schema Compatibility: Retained complete backward compatibility for existing integrations, protecting legacy scripts from schema breakdown while providing richer status information.
Synchronized Lifecycle Checkpoints: Aligned the new state boundaries directly across allocation engines, scheduling pipelines, and current connection handlers to eliminate duplicate booking requests.
When a device is set aside for a specialized team or a dedicated execution block, the rest of the infrastructure needs to know instantly. By exposing this state through the hardware telemetry API and unifying it with our session coordinators, we eliminate the scheduling conflicts and accidental overlaps that can occur when automated tasks mistakenly target dedicated hardware.
March 14, 2026
We have completed core logical components within our licensing workflows, resolved button rendering inconsistencies, and extended our inline administrative shortcuts to the device management dashboard.
Completed Subscription Workflows: Implemented missing backend logic in the Subscription Update the processing engine, ensuring that account plan modifications validate and apply cleanly across dependent platform modules.
Button Interface Rectification: Resolved layout and styling bugs affecting subscription modification elements, standardizing padding, alignment, and responsive breakpoint behavior for a polished visual appearance.
Inline Device Action Toggles: Added direct status modification support to the second column of the primary Device Action index list, allowing administrators to toggle operational parameters instantly without accessing separate configuration pages.
This update ensures that billing and plan adjustments process seamlessly without hitting partial implementation blockades or layout alignment issues. Additionally, by exposing direct status toggles right in the secondary column of the Device Action grid, infrastructure administrators can modify device routing states instantly, minimizing navigation time during busy testing windows.
March 14, 2026
Overhauled real-time socket connection management and unified backend orchestration using an industry-standardized process management structure. This update focuses on eliminating resource leaks, providing crystal-clear diagnostic logs, and securing application uptime.
Hardened Socket Lifecycles: Refactored connection initialization and teardown sequences to ensure absolute cleanup upon disconnection, preventing orphaned socket instances and memory leaks.
Defensive Connection Management: Strengthened reconnection routines and optimized event listener bindings to completely eliminate duplicate listener accumulation.
Structured Observability: Standardized log outputs across all streaming modules, delivering clear, actionable, and low-noise visibility into connections, errors, and automatic retries.
Unified PM2 Cluster Control: Introduced a centralized ecosystem.config.js deployment file to enforce uniform process names, standard environment variables, strict resource boundaries, and automated restart policies.
Unmanaged socket connections can quietly degrade server performance over time by consuming finite memory and file descriptors. By standardizing the socket lifecycle alongside a production-grade PM2 clustering configuration, the platform achieves higher concurrency resilience, self-heals predictably during infrastructure blips, and provides clean, structured telemetry for rapid debugging.
March 13, 2026
Refined test case management engine to ensure absolute execution tracking during interactive co-testing modifications. This update ensures that resume points update dynamically when altering tests with generative prompts and that newly inserted steps retain flawless sequential ordering.
Dynamic Continuation Calibration: Implemented logic to automatically update the execution resumption index (cotester_continue_is_at) whenever a test case is modified via an interactive prompt.
Fail-Safe Resume Points: Enforced precise state tracking during co-tester sessions to prevent execution offsets, ensuring the system resumes scripts from the exact intended action.
Intelligent Step Insertion: Introduced dynamic positioning logic within the test case sequence table to evaluate and place new steps precisely where they belong, smoothly handling both empty-state initializations and mid-sequence insertions.
Polished Row ID Architecture: Enhanced low-level row ID and index handling during script expansions to completely eliminate sequence duplication or index misalignment.
Modifying automated scripts mid-run with AI prompts requires real-time calibration so the runner doesn't lose its place. By stabilizing the continuation indexes and backing them with sequential step-insertion guards, testers can freely alter, insert, or expand test parameters mid-stream without risking timeline drift or corrupted execution paths.
March 13, 2026
Enhanced our time-normalization engine within build summaries and introduced centralized utility workflows for database migrations. This update ensures that transaction timestamps and exported data sheets strictly align with your personalized user interface time zone.
User-Specific Build Reporting: Updated the build detail transaction engine to parse and render timestamps according to your account's selected display time zone.
Synchronized Data Exports: Adjusted CSV report generation logic to apply localized time adjustments, ensuring that downloaded performance metrics match your on-screen dashboard view perfectly.
Centralized Migration Time Utilities: Built a suite of reusable date-time helper functions within our migration infrastructure. These utilities standardize how the platform handles time data by providing centralized routines to:
Retrieve full or commonly targeted global time zone listings.
Translate system datetimes between distinct regions seamlessly.
Fetch current timestamps directly localized to a specified target time zone.
Reviewing system logs and metrics shouldn't require complex mental math to translate server hours into your local operating context. By extending user time zone enforcement directly into CSV downloads and build overviews, engineering teams can correlate event histories instantly. Furthermore, the centralized time utility layer guarantees that future scheduling adjustments run predictably without duplicating time conversion logic across different platform modules.
March 13, 2026
Upgraded our element caching engine to support Path RID identifiers and corrected element matching behaviors within nested iframe environments. These changes ensure precise locator reuse and eliminate false-positive structural matches during test execution.
Path RID Type Support: Introduced support for the Path RID element type, updating our cache normalization comparison logic to factor in explicit path identifiers when calculating element uniqueness.
Fixed iframe Detection: Resolved a behavior where elements locked within iframe contexts were not being targeted accurately, ensuring precise selector mapping across nested web frames.
Smart Reuse Protections: Corrected a scenario where newly created text input fields were incorrectly matching and inheriting cached elements, enforcing distinct cache key generation for unique fields.
Strengthened Comparison Logic: Refined selector evaluation routines to prevent false-positive matches, ensuring that structural variations are recognized distinctly.
When automated scripts interact with dynamic forms or embedded iframe applications, minor locator overlaps can cause the execution engine to misidentify fields or reuse stale selectors. By introducing Path RID validation and fixing frame mapping, the platform guarantees that every test step interacts with the exact intended element, significantly reducing script flakiness and false execution errors.
March 13, 2026
Streamlined our core environment configurations, enhanced administrative efficiency with immediate status controls, and added robust filtering to the Process Server module. These updates focus on reducing setup friction and speeding up daily data management workflows.
Standardized Configuration Files: Renamed .env.development to a unified .env format, standardizing environment tracking across deployments and eliminating configuration ambiguity.
Inline Status Toggling: Replaced legacy status dropdowns with instantaneous toggle switches directly on the main index pages. You can now activate or deactivate entries in seconds without opening individual edit screens across these key modules:
Device Action & Process Server
Users & Teams
Orchestration Agents & Templates
Integrations, Data Center Locations & Rooms, and Device Groups
Process Server Search Filters: Introduced advanced filtering options within the Process Server module, making it easy to sort, isolate, and navigate large infrastructural datasets.
Moving configuration management to a single, standardized environment file ensures deployments are completely uniform across your pipelines. Simultaneously, replacing slow dropdown forms with direct, inline toggle switches drastically cuts down the administrative overhead required to maintain active assets, users, and device rules—giving you a faster, more responsive management dashboard.
March 12, 2026
Enhanced the user experience within the "Mark as Bug" overlay by introducing asynchronous loading feedback and structural form optimizations. This update ensures that users receive immediate clarity while integration forms dynamically fetch project-specific configurations.
Immediate Visual Feedback: Added a clean loading text indicator that activates the moment a project is selected, providing immediate confirmation that backend fields are being retrieved.
Dynamic Content Structuring: Introduced a dedicated container wrapper (project_fields_wrapper) across all integration views to cleanly isolate and manage dynamically loaded fields from static form elements.
Smooth Transition Logic: Enhanced the underlying JavaScript behavior to gracefully manage field visibility—showing the loading indicator during data retrieval and transitioning smoothly once the fields are fully rendered.
Standardized Integration Experience: Unified this loading behavior across the Device Cloud Jira view, Accessibility Testing integration panels, and all shared defect-logging views for a consistent look and feel.
When switching between projects in a bug-tracking tool, complex custom fields can sometimes take a moment to load. By adding an explicit loading state and isolating those dynamic fields, we eliminate layout stutter and remove any user confusion or accidental double-submissions caused by a temporarily blank form.
March 12, 2026
Upgraded our execution scheduling engine to provide greater transparency into automated runs. This update introduces real-time build tracking, centralized status evaluation, and device-level diagnostics directly within the job monitoring interface.
Integrated Build Tracking: Upgraded the Octopus process to dynamically fetch and map active build states to their respective scheduled jobs.
Centralized Status Evaluation: Introduced a dedicated helper function to standardize status parsing across various execution pipelines (e.g., Success, Failed, Running, Pending).
Color-Coded Status Badges: Enhanced the scheduler dashboard with clear, color-coded visual indicator badges to let users assess the health of scheduled runs at a glance.
Device-Level Query Tracking: Optimized underlying SQL retrieval queries to capture explicit device identifiers (device_id), allowing teams to track build statuses directly against the specific hardware running the test.
These updates eliminate the need to jump between scheduling panels and execution logs to see if a job succeeded or failed. By anchoring build results directly to the scheduler view—and linking them to exact device IDs—infrastructure teams can rapidly isolate whether an execution failure was a script error or a specific hardware anomaly.
Showing page 1 of 11 (107 total notes)