Support for workflow

[0hsn]

What

CHKware tool set requires a new specification that can help user design a workflow of other command and external tools, and in combination. It is expected to be an auxiliary tool that helps as a canvas when http and validation etc specs can be thought as Lego bricks.

Why

The primary reason for such tools are:

• Need of strong native tool to support test automation
• Writing workflow code to manage regression, business workflow in cumbersome and time consuming
• Managing test workflow written using programming language is complex to update and change
• It is often time consuming to setup proper message, message color, etc
• Custom made workflow system also cumbersome to navigate [TBD]

Expectations

• All sub-commands of CHKware tool can be re-usable from workflow spec
• External commands can be consumed via bash

How

• Design spec for workflow #265
• Create a base module for workflow #266
• Add support for fetch module in workflow module #267
• Add support for validate module in workflow module #268
• Add support for workflow module in workflow module #270
• Add support for variables in workflow module #269
• Add support for state variables (for data produced in between steps) in workflow module #271
• State variables should be passed in between steps in workflow module #272
• Pass arguments to tasks and validate #274
• Workflow can be used as an step in another workflow, same workflow can not be called inside #313
• Workflow should point out the in step problems found - show error messages for broken steps #314
• An error occurred inside a step, should not break the flow, the error should get reported instead. #316
• Add sub-command to run a specific workflow #317
• Support for shell tasks in workflow #348