May 18, 2026 Release Notes: Native Date Handling, Override Chrome Extension

Native Support for Date and Time Operations

testRigor now supports native date and time handling with new built-in variables and plain English commands, eliminating the need for JavaScript snippets.

This update introduces a wide range of dynamic variables for working with relative dates and times. You can now directly reference values such as nextYear, previousMonth, nextDayOfWeek, or nextHourTwoDigitsAmPm inside your tests. For example, entering a value like nextMonth or previousDayOfMonth automatically resolves at runtime without additional logic. The documentation has been fully updated with the complete list of supported variables and usage patterns.

In addition to variables, testRigor now supports format-based commands that allow you to generate and insert date and time values using natural language. You can write steps like enter us date "tomorrow" or enter month name "next month" or enter hours and minutes "in 3 hours" to produce correctly formatted values. These commands support multiple formats including US date, short date, year, month name, day of week, and time with hours, minutes, and seconds.

// Tomorrow Date, US Format  (5/19/2026)
enter us date "tomorrow" into "Type multiple lines of text here..."

// Next Year Date, US Format  (5/18/27)
enter us date short "next year" into "Type multiple lines of text here..."

For more precise formatting, new modifiers with leading zeros are also available. This allows consistent output for values such as day and month numbers. For example, enter day of the month with leading zeros "tomorrow" ensures values like 05 instead of 5.

These enhancements simplify test creation, improve readability, and reduce reliance on custom code when working with dynamic date and time values.

Override Chrome Extension via CLI

This feature enables overriding Chrome extensions via the CLI for automated testing in testRigor. If a test suite has a default Chrome extension, for example, with the new capability, you can dynamically replace this extension at runtime without modifying the settings.

From the CI/CD Integration tab, you can use the run command with Chrome extension flags to override the extension being loaded. By specifying the extension name and the corresponding file, testRigor will replace the default extension with the one provided in the command. For instance, you can keep the same extension name used in the test suite but upload a different version so that, when the test runs, the updated extension is applied automatically, and the new behavior is reflected during execution.

Caption: New Chrome extension override CLI command.

This feature also supports overriding multiple Chrome extensions in a single run, making it easier to test different configurations and scenarios without duplicating test cases or maintaining multiple test suites.