Skip to main content

Cycle 2.28.0

Released 2026-07-13.

New features​

Cycle MCP​

Building on the Cycle MCP server, this release extends the "plumbing" that connects Intelligent Discovery and Intelligent Formulation.

  • Document ingest for Discovery: Discovery can now read uploaded documents (design docs, test plans, ticket exports) and turn them into structured test specifications, so testers move through Discovery faster instead of answering every question from scratch.
  • Blue Yonder context for Formulation: Cycle MCP agents now have Blue Yonder WMS-specific context and new tools (scenario search, web selector suggestions, MOCA command execution, and WMS reasoning helpers, plus refined failure classification) so they can generate accurate CycleScript feature files for typical WMS behaviors.
  • Discovery-to-Formulation handoff: The test specifications produced by Discovery now feed directly into Formulation, connecting the two Intelligence phases for a smoother end-to-end authoring flow.

JUnit XML Reporting​

Cycle can now optionally generate a JUnit XML report for a test run, giving testers richer, industry-standard reporting when their tests run in CI systems like Jenkins.

Bug fixes​

  • Bug #11348 — Group CSV report group names. Fixed a regression where the Group CSV report assigned the same group_name to every worker group instead of the correct name for each group.
  • Bug #11349 — Group CSV report scenario names. Fixed an issue where, after an imported or nested scenario call completed, the Group CSV report could attribute later steps to the wrong scenario name in the parent scenario.
  • Bug #11350 — Group CSV report event ordering. Fixed an issue where SCENARIO_END events were sometimes written before SCENARIO_START and its steps, causing inconsistent event ordering in Group CSV reports.
  • Bug #11351 — Interleaved worker steps in Group CSV reports. Fixed an issue where steps from different workers could appear interleaved in the Group CSV report instead of keeping each worker's results contiguous.
  • Bug #11567 — Stored credentials not expanded from environment variables. Fixed an issue where stored credentials that reference environment variables (for example, ${VAR_NAME}) were not expanded by the Cycle engine when used in test steps.
  • Bug #11644 — Output folders for test cases with multiple examples. Fixed an issue where data-driven test cases with multiple examples each created a separate timestamped output folder instead of running under a single test case execution context, and where the "file URI" field in custom reports displayed "null" instead of the test case name.