Skip to main content

Cycle 2.29.0

Released 2026-08-17.

New features​

Blueprints​

Blueprints are a declarative way to set up and tear down the test data a test depends on. A blueprint is a YAML file that describes the records a system under test needs, such as an item, a customer, or an outbound order. Cycle creates those records before a test runs and removes them afterward, so tests start from a known state instead of relying on data that happens to already exist.

  • Run a blueprint from the CLI with --blueprint, validate one with --validate-blueprint, and tear down the data a blueprint created.
  • Run a blueprint offline against a local database with -offline, which does not require a connection to the system under test.
  • Call blueprints from a feature file using native CycleScript steps, so data setup lives alongside the test that needs it.
  • Author and run blueprints through Cycle MCP with the blueprint_validate, blueprint_run, and blueprint_teardown tools, plus a guided onboarding prompt.
  • Connect to MOCA, SQL, REST, MongoDB, and flat file sources, with SQLite supported for local runs.

Cycle MCP: Intelligent Discovery​

Discovery gathers information about a system under test and turns it into test plans. This release brings the questionnaire and discovery map experience into local Cycle Intelligence and combines the separate Discovery inputs into one guided flow.

  • A single guided prompt, begin-discovery, walks a tester through Discovery from start to finish and can be resumed later.
  • Questionnaires run locally and store their answers, which Cycle then runs through a discovery map to produce insights.
  • Discovery generates test plans as Markdown files that hand off directly to Formulation.
  • Document ingest and questionnaire answers feed the same flow, so a tester is prompted for whichever input sources apply.

Cycle MCP: Intelligent Formulation​

Formulation generates executable test cases from input sources such as prompts and test plans. This release adds refinements to the Formulation process and improves the handoff from Discovery outputs.

  • Cycle MCP reads a Discovery output bundle, exposes the test specifications it contains, and reports a readiness signal for each one so a tester can see which specifications need attention before conversion.
  • A guided prompt converts selected specifications into CycleScript tests, then executes each generated test to confirm it runs.
  • Cycle MCP now executes every CycleScript step individually rather than web steps alone. Agents can work through a system under test one step at a time, which supports exploratory testing and more accurate test generation.
  • CycleScript compiler diagnostics now carry machine-readable codes, so an agent can react to a specific error rather than parsing message text.

JUnit XML report screenshots​

JUnit XML reports now include screenshots in a form that CI systems can display. Jenkins and Azure DevOps are both supported, so a tester reviewing a failed pipeline run sees the screenshot alongside the failure.

CycleScript debugging​

The Cycle Testing Kit supports debugging a Feature File. Set breakpoints in a .feature file, then step through or continue the run using the standard debug controls. Debugging is driven from the Cycle Testing VS Code extension, version 1.17.0 or later.

Bug fixes​

  • Bug #11719 — Project settings not initialized. Fixed an issue where settings for a project created in an earlier version were not initialized correctly, so defaults such as the WebDriver timeout and finder strategy were missing.