Cycle 2.24.0
Released 2025-11-03.
New features
MOCA Connectivity Utility
We have created a small network utility to help diagnose MOCA connectivity issues in customer environments. It performs a battery of diagnostic checks and creates output that we can review after a user provides it to us. Details on how to get the utility, run it, and extract the output can be found in the Knowledge Base article.
Bug fixes
- Bug #1771 — Error message for multiple
.cycprojfiles. Updated the error message that appears when Cycle will not open because a project directory contains two.cycprojfiles. It now reads: "Error: Found multiple .cycproj files in project directory. Only one .cycproj file is allowed in a project directory". - Bug #2280 — Infinite looping when using Groovy with Cycle lists. Fixed an issue where Cycle reset the iteration index for a list whenever Groovy was called. Cycle now preserves the iteration index for a list when it calls Groovy, no matter what modifications the Groovy script makes to the list. If the iteration index is 2 before Groovy is called, it will be 2 after Groovy is called, even if the list has all elements removed.
- Bug #4352 — CLI not generating a report when no
-pargument is provided. Cycle now uses the current working directory as the project directory when the project directory is not explicitly specified by the user. - Bug #7838 — Stuck loading icon in the Report Dashboard. Fixed an issue where the Report Dashboard showed a stuck loading icon when a While loop used a wait step.
- Bug #7880 — Step suggestion breaks when using backspace. Fixed an issue with completion logic for matches with literal tokens that start with ordinals, such as "start". The case where an ordinal token begins a longer literal token is now handled correctly.
- Bug #7929 — Step assist results for the Trim keyword. Fixed step assist so that it shows the appropriate steps when the Trim keyword is used.
- Bug #8118 — Strings containing
$in the replace variables step. Fixed an issue where inserting a string that contains a$caused problems with the Cycle replace variables step. - Bug #8939 — Incomplete uninstall when VS Code is open. Added VS Code to the list of processes that the installer will close. This currently does not prompt to save changes before closing, so be sure all changes are saved within VS Code before selecting this option in the installer.
- Bug #8987 — Tags not auto-populating in CVT files. Fixed an issue where tags did not auto-populate in CVT files.
- Bug #9086 — Step suggest ordering differs between VS Code and Desktop. Fixed an issue where Step Suggest offered a different order of steps in VS Code than in the desktop application.
- Bug #9805 —
cycle-cliand Ctrl+C in Windows Terminal. Fixed an issue wherecycle-clidid not handle Ctrl+C gracefully in Windows Terminal. - Bug #10048 — Users not logged off by the close MOCA connection step. Fixed an issue where users were not logged off by the step
I close MOCA connection. - Bug #10144 — Step incompatibilities between 2.22 and earlier versions. Fixed an issue with parameter types between Cycle 2.22 and earlier versions where parameters included in quotations were not recognized as valid values. During parameter type checking, Cycle now checks the contents of quoted tokens to see if they are valid numbers, according to the desired number types of the steps. (See also Bug #10046 for the related input focus issue.)
- Bug #10168 — Variable replacement in XML attributes. Previously, variable replacement was only supported for the XML body, and variables in attributes were not replaced. Cycle now supports variable replacement in XML attributes.
- Bug #10169 — Implicit hovers and clicks in the plugin. Fixed an issue where implicit hovers and clicks on elements in the plugin caused failures.
- Bug #10170 — CLI not reporting Scenario Outline failures. The CLI reports scenario outline failures correctly again.