Top Seven Underrated Considerations When WMS Testing

Here at Tryon Solutions we have many grizzled warehouse management software (WMS) veterans, most of whom are also experienced in the realm of software testing, and more specifically, test automation.  I polled, poked, and prodded our grizzliest of grizzled WMS vets to find out what is most often overlooked and underrated when testing a WMS.

 

  1. Data management. A truly automated test includes data setup and housekeeping, and this part is almost always the most work.  An automation engineer working with a cross-functional team designing test cases should have the “data conversation” when creating the tests, as using valid data that mimics the “real world” is just as crucial as the warehouse business process itself - and having to manually create and reset test data is not reaping the full benefits of test automation.

 

  1. Using dedicated testing environments. Manual testers plugging away in the same environment used by automated tests often results in false positives, data nightmares, and other chaos…For example, if a manual tester deletes a location that is also being used by an automated test then the automated test will probably fail when it moves inventory to a non-existent location.

 

  1. Writing tests for more than one environment. When creating test scripts/features they should – ideally - be able to work across various WMS environments within a company assuming the warehouse business processes aren’t drastically different.  I’ve heard horror stories of automation engineers writing a suite of test scripts against one environment assuming that they will work elsewhere, and then later finding they can’t be used at other warehouses due to small nuanced differences in processes (which could be accounted for in the script by making it more flexible), hardcoding when variables should have been used, and/or different data configuration elements.  Its easier to write tests from scratch against a variety of environments, then to go back and modify an entire test suite after the fact.

 

  1. Ensuring the testing team is truly cross-functional and that all have “bought in” to the program. For example, an automation engineer isn’t going to write scripts/features to test out the terminal receiving process that are worth a salt without the involvement of at least one employee from the loading dock (in this case the subject matter expert) who is intimately familiar with the company’s inventory receiving process and knows from experience what is likely to go wrong, what needs to be validated, and also believes in what the automation engineer is doing.

 

 

  1. Creating regression and performance tests for the most critical business processes while focusing on their most common paths (aka smoke testing) before fleshing out the test suite with edge cases, negative tests, and more permutations. Target what absolutely MUST work first.  For example, an online Blu-ray store should consider starting off their test suite with an order fulfillment test for their best-selling movie.  They should also – and admittedly this is optional - burn all copies of the Cats movie.

 

  1. Performing true end-to-end tests complete with related integrations, in addition to the modular test case suite.  Its critical to validate the system from start-to-finish as a user in order to check the full application flow as well as the accuracy of the data movements and other integrations and connections in-between.  The modular tests can be used to help create the end-to-end tests if they were properly designed.  Be sure to choose a test automation solution that makes creating end-to-end tests easier, and our product Cycle does just that.  For that reason - among many - we are Blue Yonder's choice as a test automation provider.

 

  1. Buying the strongest cuppa joe available by law, and if that doesn’t cut it then look into illegal coffee options.

 

Did we overlook something else frequently overlooked (and underrated) when WMS testing? Let us know on social media @TryonSolutions!

This post was written by:

James Prior
Technical Pre-Sales Consultant

James has been working in software pre-sales and implementation since 2000, and has more recently settled into focusing on technical pre-sales. He takes care of our hands-on demonstrations, and eagerly awaits your request to see our Cycle test automation software in action. Drop him a line at: james.prior[at]tryonsolutions[dot]com.

Recommended Content

 

 

Global Engineering Group Upgrades WMS with Tryon Solutions & Cycle

Global Engineering Group Upgrades WMS with Tryon Solutions & CycleOur customer is a global, high-technology engineering group founded in 1862. The company is a leader in tools and tooling systems for metal cutting; equipment, tools and services for the mining and...

Checklist: Deciding which Tests to Automate

Essential Checklist for Deciding Which Tests to Automate To automate or not to automate?That is the question a lot of test professionals ask themselves- when deciding what tests should be run by software and which ones are best performed by people?To help, we've come...

Cycle & Behavior Driven Development: How It Works Demo

What We Covered: High level explanation of Cycle as a behavior-driven test automation solution Overview of advantages including collaboration, lower maintenance, streamlining, and how Cycle is used to mitigate deployment risk Overview of Cycle interface, syntax, key...