Skip to content

Support for workflow #264

Open
11 of 16 issues completed
Open

Description

@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

Activity

  1. pinned this issue on Nov 14, 2023
  2. self-assigned this
    on Nov 14, 2023
  3. moved this to In Progress in chkware/clion Nov 14, 2023
  4. changed the title [-]Support for worflow[/-] [+]Support for workflow[/+] on Feb 4, 2024
  5. moved this from In Progress to Done in chkware/clion Oct 23, 2024
  6. reopened this on Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions