Friday, June 29, 2018

A Design Pattern for Automation Repeatability

Some of my customers are trying to design an automated script to perform specific workflows with a predicted outcome. Unfortunately, the automated workflow they want to execute has many variations in their environment, and they're having trouble creating a dynamic, automated script that handles environment deviation.

So, how do you code it? The short answer is, you don't code for variation; you code for consistency and define the variation. When tasked with an automated process, customers will code step by step until they reach a step that has variations, then they'll code a ton of conditionals to account for all the disparities. There is a better way to do this that will give you clear, defined end results: automated states.



from DZone.com Feed https://ift.tt/2KggDHC

No comments:

Post a Comment