Project structure

Project teams should use a consistent directory structure so that Feature Files and the related content can be moved between development PCs and rolled out to other environments. The root directory used by Cycle should also be setup as the Resource Directory within the Cycle application. If Cycle is being used to support more than one project, then the name of the Cycle directory should indicate the project. The example below shows the directory structure on a PC supporting both a 2010.1 WMS project and a 2013.2 WMS Project. Please note that not all necessary files are represented in the directory structure, but representative examples are provided.

Cycle_WM_2010.1 (Resource Directory)

  • /Features
    • Picking.feature
    • Receiving.feature
    • /Utilities
      • Environment.feature
      • JDA_WM_Utilities.feature
      • SAP_Utilities.feature
  • /Images

    • Wave_Operations-Plan_Wave_Button.png
    • Wave_Operations-Allocate_Wave_Button.png
  • /Datasets

    • /Picking

      • cleanup.msql
      • locmst.csv
    • /Receiving

      • cleanup.msql
      • locmst.csv
  • /DataExtractModels

    • pre-picked_orders.extract
  • /Group_Tests

    • pickinggroup.rbt
    • /csv
      • rdt_1-4.csv
      • rdt_5-8.csv
  • /Output

Cycle_WM_2013.2 (Resource Directory)

  • /Features
    • Picking.feature
    • Receiving.feature
    • /Utilities
      • Environment.feature
      • JDA_WM_Utilities.feature
      • SAP_Utilities.feature
  • /Images

    • Wave_Operations-Plan_Wave_Button.png
    • Wave_Operations-Allocate_Wave_Button.png
  • /Datasets

    • /Picking

      • cleanup.msql
      • locmst.csv
    • /Receiving

      • cleanup.msql
      • locmst.csv
  • /DataExtractModels

    • pre-picked_orders.extract
  • /Group_Tests

    • pickinggroup.rbt
    • /csv
      • rdt_1-4.csv
      • rdt_5-8.csv
  • /Output

results matching ""

    No results matching ""