Epic | Implement Functional Testing

[ReedClanton]

Rationale

Provides proof of functionality.

Owner

@ReedClanton

Stakeholder Point of Contact

@ReedClanton

Dependencies

I think it's likely a good idea to have a full set of unit tests prior to embarking on this. Thus #31 should be done first.

Description

Create functional 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. A full unit test suit of unit tests will have been written using the shellspec library prior to working this, so that may be used as a reference.

Issues

• Create & Document Functional Testing Stadards #34

Blocked By

• Epic | Implement Unit Testing #31

Acceptance criteria

• All documentation of unit tests should be complete:
  • This includes setting and documenting standards.
• All tests should meet all functional testing standard(s).
• GitLab actions should run all tests and prevent merging when there are any failures, or any standards aren't met.