Epic | Implement Unit Testing

[ReedClanton]

Rationale

Provide confidence of product quality.

Owner

@ReedClanton

Stakeholder Point of Contact

@ReedClanton

Dependencies

None.

Description

Create unit testing standards, document them, create tests that follow them, then run those tests via CI/CD.

Context

Moving from bash_unit unit testing library to shellspec.

Issues

• Create Basic Set of Unit Tests of createHeaderFooter #13
• Convert Unit Test Library from bash_unit to shellspec #23
• Get shellspec Unit Tests Running on GitHub Runner #24
• Create Unit Tests of shellName() and Any Util Code #32
• CI/CD | Run shellName() Unit Tests #33
• Create Unit Tests of log() and Any Util Code #36
• CI/CD | Run log() Unit Tests #37
• Create Unit Tests of output() and Any Util Code #38
• Create Unit Tests of backUp() and Any Util Code #39
• Create Unit Tests of checkRequiredOpts() and Any Util Code #40
• CI/CD | Run backUp() Unit Tests #42
• CI/CD | Run checkRequiredOpts() (verifyInputProvided()) Unit Tests #43
• CI/CD | Refactor How GitHub Actions are Run So They're Efficent #49
• CI/CD | Determine why --fail-low-coverage Always Fails in Pipeline #53

Acceptance criteria

• All documentation of unit tests is complete:
  • This includes setting and documenting standards.
• All unit tests must meet all unit testing standards.
• All code should have 100% coverage:
  • The library used by shellspec to calculate code coverage doesn't work very well, so some files may say that coverage is less than 100%.
• GitLab actions should run all unit tests and prevent merging when there are any failures, or coverage isn't 100%.