Add Unit Tests
Create unit tests using NUnit. Some tests could include:
- Parser output using many different sample inputs.
- Adding/removing macros, memes, etc.
It would be better to have a separate project for the tests so the code doesn't get muddled.
Would this be something we want after a database implementation? (Update: my bad this shouldn't matter since it isn't an integration test)
Not necessarily, but it may be preferable. Having the database implemented would let us test the database itself.
Some of the code is hard to test due to tight coupling. For example,
Parser.ParseInputs is coupled to reading bot data. I'll start on improving this.
I made the necessary changes to test the Parser and added a project for conducting tests. I'll double-check everything, merge it in, and add documentation on how to run the tests later.
Deleting a branch is permanent. It CANNOT be undone. Continue?