As reported in issue #192, the contribution relating to running tests with Github Actions means that not all tests are being run that would be run using unittest. This has meant regressions are not being adequately caught.

Need to make sure that the entire test suite is run in the Github Actions, in the mean time manually verify functionality with python3 -m unittest prior to each release.