Implement functional testing

[mcdonnnj]

🐛 Summary

Once #8 is merged a large number of the tests defined in this repository will be disabled. This is due to the fact that they were written based on working out of a running Docker orchestration and not stand-alone package testing. Given how our GitHub Actions testing is written this is not readily implementable for this project. It is also desirable to have stand-alone testing for the Python package if at possible.

Expected behavior

Using our GitHub Actions workflow or running pytest locally results in all tests that are defined passing.

implementation notes

When testing trying to get them running as-is I first added pyfakefs to insert an appropriate configuration file at the default location (/run/secrets/admiral.yml). Once I was able to do that I then ran into the problem that it needs a running redis server.

[king-alexander]

This will be easier to tackle once all the various components are split up into their respective repositories. See cisagov/admiral-docker#5 and cisagov/ansible-role-admiral#3.