Cycle Labs Releases Cycle 2.30, Advancing Intelligent Test Creation and Developer Workflows
Raleigh, NC (September 24, 2026): Cycle Labs, a leader in enterprise test automation for complex supply chain and ERP environments, announced the release of Cycle 2.30. The release advances how teams discover and formulate tests for complex enterprise systems while introducing Cycle CLI v2, a new default CycleScript runtime, expanded debugging capabilities, and improvements to the Cycle Testing extension for VS Code.
At the center of Cycle 2.30 are new Intelligent Discovery capabilities for Blue Yonder WMS. Discovery can now answer questionnaire items directly from a Blue Yonder WMS configuration export, reducing the need for testers and subject matter experts to manually answer every question. Teams can place an export in the project’s Config-Export folder, where Cycle scans the configuration tables and uses that information as another input source for Discovery.
The configuration scan also makes its reasoning traceable. Each answer records that it came from the scan and identifies the configuration used to determine it, so testers can review the source rather than simply trust the result. When the configuration export provides an answer that differs from one previously entered manually, Discovery treats the export as authoritative and identifies both the new and previous values.
Cycle 2.30 also includes several Cycle MCP refinements that strengthen Discovery, Formulation, and agent-driven testing workflows. Web selector lookups now use a single element map as the source of truth for locators, while improved menu path resolution helps agents retrieve elements for the correct screen. A new get-context tool gives agents direct access to named Cycle context, and updates to run_step allow steps executed through Cycle MCP to use the same saved connections and credentials available during a standard test run.
Together, these enhancements provide agents with more consistent application context and execution capabilities as they move from understanding a system to formulating and executing tests.
Cycle 2.30 also makes Cycle CLI v2 the default command surface, introducing a more extensible structure built around subcommands that can expand as new capabilities are added. New commands let testers create feature files, playlists, group tests, API requests, and Blueprints from built-in templates, as well as run saved API requests directly from the CLI. This extensible architecture will make more of the core tools in the Cycle Testing Kit accessible through the CLI, not only to testers and developers, but also to AI coding agents.
The release also makes Cycle’s new CycleScript runtime the default execution engine for every installation. The new engine was available in earlier releases when explicitly enabled, but Cycle 2.30 marks its transition to the standard runtime for CycleScript. Existing tests, playlists, and group tests are designed to run and report the same way, with no changes required to how testers write or organize their tests. Customers who encounter different test behavior after upgrading from Cycle 2.29 are encouraged to report it to Cycle Labs.
“Cycle 2.30 continues our focus on making intelligent test creation more practical for the complex systems our customers need to validate,” said Andrew Knight, Senior Director of Product and Engineering at Cycle Labs. “From using existing configuration data to accelerate Discovery to expanding what testers and AI coding agents can access through Cycle CLI v2, we’re giving teams better ways to turn what they know about their systems into reliable, executable tests.”
CycleScript debugging also expands in the Cycle Testing extension for VS Code 1.20 with data breakpoints. In addition to pausing execution at a specific line, testers can now pause a run when the value of a variable changes. The debugger stops on the step that made the change and identifies the variable along with its previous and new values, helping testers pinpoint when and where test data changes during execution.
Beyond debugging, VS Code 1.20 also improves the everyday authoring experience with new visual editors for Cycle project and user settings files. Instead of editing these settings as raw text, testers can work with interfaces similar to the settings editors in the Cycle Desktop IDE. The extension also introduces unique icons for Cycle file types, making different files easier to identify throughout a project at a glance.
Cycle 2.30 includes additional enhancements to Blueprints, authentication, reporting, and execution safeguards. The Blueprint library location can now be managed as a typed project setting, and Blueprint paths resolve consistently from the command line across both CycleScript execution engines. Desktop runs now validate the reporting Data Store before executing Feature Files, while CycleScript provides clearer error reporting when If block clauses are repeated or appear out of order.
Users are encouraged to update to Cycle 2.30 and the latest Cycle Testing extension for VS Code to access the newest capabilities and improvements. For complete details, refer to the user manual or contact the Cycle Labs Customer Care team at help@cyclelabs.io.
About Cycle Labs
Cycle Labs helps enterprises deploy change without increasing risk. The company builds test automation software for complex supply chain and ERP environments, so teams can move faster, validate continuously, and challenge the assumption that stability requires slowdown. Cycle Labs is the creator of the application-agnostic, end-to-end Cycle® Continuous Test Automation Platform, supporting WMS, ERP, TMS, and retail systems. With Cycle, organizations accelerate innovation while protecting the systems they rely on most. Learn more at cyclelabs.io.
Media Contact
Jodi Coverly
Senior Marketing Manager
jodi.coverly@cyclelabs.io
