Story (Required)

As a contributor to the gitops-must-gather, I want to be able to run tests to check my work when I make code changes. 

Background (Required)

Currently there are no tests (unit or e2e tests) as part of the gitops-must-gather.

Out of scope

• Changing the functionality of the gitops-must-gather.
• Adding tests to CI (separate story)

Approach (Required)

Make a new folder testing and add tests for the must-gather component. At minimum it should check that the script runs (and writes to error file for cases when it shouldn't run, such as when cluster isn't an openshift cluster and/or when kubectl or oc aren't installed) and writes output information to files. Ideally it should also check that all the commands either ran successfully or output an error to the error file. 

Dependencies

None. 

Acceptance Criteria (Mandatory)

• add unit & e2e tests in a new folder in the gitops-must-gather repo. 

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met