Skip to main content

Cycle 2.16.0

Released 2023-11-27.

New features​

API Call Execution from the Editor​

Building on the API call functionality introduced in version 2.15, version 2.16 introduces the ability to execute API calls directly from the editor. Key benefits include:

  • Validation of API calls: You can now validate the configuration of your API call directly from the editor before executing the call from a feature file.
  • Enhanced visibility: Gain better visibility into the API response as you work on your feature files.
  • Variable list and sample data: We've retained the variable list panel in the API editor for quick reference. A new "Sample Data" panel lets you provide data for the execution of the API call directly from the editor. Sample data values are available for variable substitution but are not stored with the project, so sensitive data such as tokens will not be committed to your repository.

Bug fixes​

  • Bug #4578 — Error 933 with Oracle databases. Fixed an issue where error 933 was returned when running SQL files against an Oracle database.
  • Bug #4660 — Stop button not working with restart failed worker. Fixed an issue where the stop button did not work when "restart failed worker" was selected.
  • Bug #4773 — Extra debug information before test execution. The Cycle 2.15 cycle-cli command generated extra debug information before test execution. We addressed this by suppressing the additional logging configuration from the console when running cycle-cli. (See also Bug #5001.)
  • Bug #4849 — Tokens cached before subscription assignment. When logging into Cycle before being assigned to a subscription, the token is no longer cached.
  • Bug #4852 — Server tuning settings not saved. Fixed an issue where server tuning settings were not saved after exiting Cycle. (See also Bug #4856.)
  • Bug #5120 — Application not fully exiting. Fixed an issue where the application did not fully exit when "Close apps after execution" was toggled off.