No testing

[Laura7089]

As of right now, there are no tests whatsoever in the repo. This is mostly down to the fact that our primary IO - discord.py is difficult to test against since it provides no test suite (that we know of). Additionally, we make a lot of calls to google, twitch and twitter APIs which are in turn difficult to test against.

However, we have several areas of functionality which actually don't call any of the above and so can likely be unit tested well. Plus, there are ways of testing the functionality of IO-heavy operations; for example, mocks or snapshot testing.

[Laura7089]

Python provides built-in support for testing with

• https://docs.python.org/3/library/unittest.html
• https://docs.python.org/3/library/unittest.mock.html

We could create a tests directory in the root with a mirrored module layout, then insert tests into that as we write them.
Or, we could put tests in the source directory alongside the code they're testing, in files like test_strTyping.py for easy import management.

Then, a simple python -m unittest discover src or python -m unittest discover tests would run them all and report the results.

[Laura7089]

Linking to #85, this could then also be added to CI which could in turn block PRs until tests pass. We could also add a minimum test coverage barrier (if we really hate ourselves).

[Laura7089]

A testing library for discord.py exists at https://pypi.org/project/dpytest/