Stay consistent in naming Cycle files, images and variables.

Stay consistent in naming Cycle files, images and variables.


Teams that use differing names for core elements often encounter difficulties when reading other developer's Cycle tests.


Sticking to the following naming conventions will help add clarity and greater readability to Cycle projects:

Feature File names

  • The file name for a Feature should be the same as the Feature that the file contains. Example: Picking.feature
  • Feature Files that contain Scenarios meant to be imported into many other Features should be created in the Utilities directory within the Feature directory and the word "Utilities" should be included in the file name.
  • If a group of Features are related or dependent upon each other, the names should contain a common root within the name. For instance, a set of Features created to support an enhancement would all contain the enhancement within the name.


  • The name of a Feature should be short, but must also be descriptive enough to convey the purpose of the test Scenarios contained within. If the Feature is being used to to support a specific enhancement or issue, the enhancement name or issue number should be part of the Feature name.


  • If the image is specific to a single Scenario, the name should follow the format: Feature-Scenario-Description.png
  • If the image is for a JDA screen and can be reused, the name should follow the format: Screen-Description.png (example: Wave_Operations-Plan_Wave_Button.png)
  • If the image is for an extremely common image, the OK button for instance, the name should follow the format: Description.png (example: OK_Button.png).


  • MOCA Environment Variables created in the Environment.Feature File should be assigned with a standard prefix, example uc_cyc. Full example uc_cyc_usr_id. This helps differentiate Cycle assigned MOCA Environment variables from JDA WMS environment variables.
  • All other variables should be all lowercase and multi-word variables should be connected by underscores (example: pick_list_id)
    • Related Articles

    • Structuring Feature files.

      Problem With multiple developers writing tests on the same project, inconsistent Feature File structure can lead to overlaps in test coverage and reduce test readability. Solution Adopting a modular approach Many common computer interactions are ...
    • Make Cycle Features easier for others to understand.

      Problem Even well written Cycle Features can sometimes seem unclear to a new user. Solution By including comments at the beginning of your Feature and within Scenarios, you can lay out all pertinent details for a reader without needing to use Cycle ...
    • Aligning terminal Steps with Operator behavior

      Problem My terminal-based Cycle Steps don't always perfectly coincide with the actions a human operator performs on their device. Solution There are 3 terminal Steps that can provide a clear picture of the business process and end user operation. ...
    • Getting Started with Cycle 2

      Log In to Cycle Cloud In order to get started with Cycle 2, you will need to sign up for a Cycle Cloud account, and then download Cycle 2 from Cycle Cloud. The sign up process requires you to verify your email address. Please note, the email address ...
    • How to load and clean up test data efficiently in Cycle.

      Problem In order to properly evaluate system behavior it is required that known inputs produce desired outputs. This is especially critical when working with the JDA WMS due to its multitude of configuration options that drive specific system ...