Issue 38 - adding unit tests

[Holdrick]

Contributes to #38 (add issue number here. i.e. #302)

What did you do?

• Added unit tests to the analyse_text and check_words methods in main.py

• Extracted db creation to a method that's called in each required method so the db creation can be mocked out in unit tests

  Why did you do it?

  Adding unit tests helps protect us from future changes that break previous ones

  How have you tested it?

  I did some manual tests to see if my change broke anything

  Were docs updated if needed?

• [ ] No

• [ ] Yes

• [x] N/A

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] My changes generate no new console logs
• [ ] Fixes entire issue
• [x] Partial fix for issue

[Holdrick]

Looks like theres a conflict with the old test. The test was written before token authentication so I reworked it to pass with the present production code

[Holdrick]

The unit tests are mostly independent. There's only a couple things in main that could be refactored:

• You still need to be in the virtual environment
• The client variable aka the couchdb Server class initialised on line 98 (this seems okay for now. I've tested the unit tests without the docker container running)