Continuous Testing of the plug-in

[zFernand0]

Tasks:

• [ ] Each branch/tag is install-able (using zowe plugins install) and operational from the corresponding @zowe/cli@tag
  • latest -> latest; zowe-v1-lts -> zowe-v1-lts; next -> next;
  • ~lts-incremental -> lts-incremental~; ~lts-stable -> lts-stable~; ~daily -> daily~
  • This also proves that the plugin introduces a unique (non-conflicting) command group
  • Note: plugins need to provide workarounds for pre-requisites (e.g. ODBC Driver for DB2)
• [ ] Each branch-tag can be uninstalled (using zowe plugins uninstall) without any issues and/or warnings after the fact.
• [ ] While testing, the CT pipeline should be able to override profiles using ENV vars and options on the command line
  • This includes order of precedence with base profiles and different config layers.
  • Needs some research on how to run system tests without affecting the plugin repo
• [ ] While testing, verify that all output of the commands is contained in the --response-format-json version of the output
  • This proves that the output is written using response.console unless handlers do some kludge to put it all in it.
• [ ] Validate that the plugin works vNext releases of Zowe with a grace period of 30 days.
  • The pipeline will accept failures and notify the plugin team (via email or git issue) about such problems.
  • If the pipeline still fails after 30 days, the plugin will be marked as non-conformant for the release it was tested with.

[github-actions[bot]]

Thank you for raising this issue. The community has 90 days to upvote 👍 the issue. If it receives 5 upvotes, we will move it to our backlog. If not, we will close it.