BY WMS Library Release v 3.4 / 2024-07-01

The WMS Library test cases have been updated to ensure they run for Blue Yonder 2021. This includes a new Locators file specific to the Blue Yonder 2021 version. 

Split large reports into smaller reports using our custom template. The BY WMS Library now includes a PowerShell script in the Documentation/User Guides/Reports/ folder that can be executed locally or through a pipeline to split a large Cycle report into smaller reports and rename the resulting file based on the content. This helps users more easily read large Playlist reports by breaking them down by Feature file. For more information on how to implement this feature, please see the "Cycle HTML Report Splitting - User Guide" located in the Documentation/User Guides/Reports/ folder. 

10+ Report templates that can be used for creating custom Jasper reports.

Developer Utilities have been relocated from the Environment.feature file to a separate Utilities file to better allow for customizations based on customer needs. 

Updates to ensure users are able to cleanly log in to the terminal and web interfaces if a test is aborted.

Accelerate your implementation of a performance test with a base framework that can be easily expanded upon. This framework includes logic for locking values for each of the processes to prevent work overlap across different devices and several base .msql scripts for looking for and assigning work relevant to the given process. 

Base tests and test data generation feature files have been created for: 

• ASN Receiving
• Non-ASN Receiving
• Putaway
• Pallet Picking
• List Picking
• Carton Picking
• Trailer Loading
• Closing and Dispatching a Trailer
  

Need a focused view of what is happening during your test case to help save time and pinpoint issues? New developer logging utilities allow developers to write customized messages to a .log file.  By assigning a “log_line” string and executing the 'Log to Developer Logging File' scenario, these new utilities can help identify common places in the code where things may go awry. Default developer logging has been added for some common bottlenecks, including: 

• Returning MOCA statuses and error messages
• Iterating through input variables 
• Executing Dynamic Data assignments
• Creating and sending JSON/XML files
• Starting and stopping a test
• Initial attempt to log out of the terminal and confirmation when the terminal is fully logged out
  

This change allows XML template files to contain numbers and dashes and removes the requirement that an XML template file must contain the test case within its name.  This allows a single XML template file to be used across multiple test cases.

Base utility updates have been implemented to allow the Test Case Input file to be nested in a sub-directory of "Test Case Inputs". Specifically, this fix allows the dynamic data logic to be able to find nested test case input files appropriately. 

Note: this change only allows a set of subdirectories under “Test Case Inputs” that matches the subdirectories defined in the “directory_load_path” variable.

All locator files are now stored as CONF files instead of CSV files. The methodology for importing the locators now allows for layering as is specified in the “directory_load_path” variable.

The “directory_load_path” variable has been added as a default variable to be included in the Environment CSV. This will help to provide clarity on how to update the layering architecture per environment. 

Test Specifications have been given a facelift. The updated design focuses on ensuring that relevant business requirements are easy to find in one location. This includes adding sections for valid test case variable assignments and ensuring data requirements are defined per test case step.

Terminology updates have been made to the user guide, upgrade notes, and release notes to reflect usage of the term “Test Library” instead of the historical usage of “Bundle”. This aligns with the Cycle Labs standard terminology moving forward.