TestSlide

This is mostly manual as described at RELEASE.md. We need to: Using semantic versioning, be able to do major, minor and patch releases, calculating the new version based on the previous. Unify version at setup.py and docs/conf.py. Ensure Travis CI build is OK for new release. Ensure readthedocs.org build is OK for each release.

Let's add an option , which'll look over issued warnings during test execution and fail them if warning issued. This can probably be done easily by patching Python's warning method and checking if it was called. I see 3 cases to check for warnings: 1 - When importing test modules. 2 - When running individual tests. 3 - On shutdown. For 1 & 2, this should be easy, not sure about 3. An important feature of this, is to allow include / exclude paths to accept / ignore warnings. Eg: if a warning came from a third party library, there's sometimes little one can do, and we should ignore it. If warning came from the code being tested, it should surface.

What: Upgrading to Typeguard 3.02 Why: Keep Testslide up to date How: Pin Typeguard version to 3 (3.02 is latest version at this time) Update Typeguard mock to instead mock Update Typeguard mock target to internal Update exception handling to catch Misc. Update string concatenation to use f-strings instead Typo in unittests: StritMock -> StrictMock Remove commented out code Add some comments on how why we mock out Typeguard with wrapped calls Risks: Some error message formats have changed Checklist**: [x] Added tests, if you've added code that should be tested [x] Updated the documentation, if you've changed APIs [x] Ensured the test suite passes [x] Made sure your code lints [x] Completed the Contributor License Agreement ("CLA")