Implement Functional Testing

[MattsonCam]

          Also for a tool or package, we will need some sort of tests here. Probably do not need it to merge this first PR, but future PRs might need to have test units.

Originally posted by @MikeLippincott in #1 (comment)

          Great comment! I'd **strongly recommend adding testing** if possible to help ensure the code delivers the promised functionality. Testing is one of the best tools we have to defend against unexpected behavior!

I always urge for testing to be added along with functionality to help ensure code coverage as things change. Foregoing this means there's a chance of forgetting to do so later. Adding tests upfront is an investment towards development velocity and trust in the code longer term - especially if things might change or there's a chance that this project will be used in others as a dependency (increasing the risk vector for things to go wrong).

Originally posted by @d33bs in #1 (comment)

Based on the above comments, I plan on testing the tool to make sure it works as intended with different inputs

[MattsonCam]

This was implemented in #1.