Create new unit tests for Evennia

Brief summary of issue / Description of requested feature:

This is an issue originally started under hacktoberfest but extended beyond that. The issue is for expanding Evennia’s unit test coverage. This is also a great way to learn some of Evennia’s systems under the hood.

Steps to reproduce the issue / Reasons for adding feature:

1. Go to the coveralls page for Evennia
2. Find an Evennia module under evennia/ that lacks unit test coverage. a. Exception: /evennia/game_template/* is not much point to unit test b. Exception: Any /migrations sub directories should not have unit tests
3. If you are new to Evennia, please see the Getting Started instructions on how to set up Evennia locally - you can just create an empty game folder.
4. See Evennia’s How to unit test Evennia page for more info. Tests of this issue will run by executing evennia test evennia from the game dir.
5. If no tests.pyfile yet exists in the sub-package in question, add it and then add your test to it. It will automatically be picked up by the test runner. See other tests.py in the Evennia repo for help.
6. Here is help on django unit testing should you need it.
7. If you are unsure about how GIT/PRs etc work, check out the Forking Evennia page.

Expected result of feature

We are currently at ~53%~ 64% unit test coverage, why not expand that?

Extra information, such as Evennia revision/repo/branch, operating system and ideas for how to solve / implement:

This is against master branch. Ask in forum or chat (#evennia on irc.freenode.net) if you have any questions on how to test a particular system - we are happy to help!

<bountysource-plugin>

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>

[Griatch]

@Keda87, @vaibhavsingh97 That’s great! I updated the issue with some more info. 😃

[Griatch]

@selberhad Oh, haven’t looked at the detailed coverage in the while. I updated the root now, so you should be able to see the source code. Thanks for the heads up!

(The develop branch coverage on coveralls.io is also weird. If you run locally, the coverage for that branch is 66%, but on coveralls.io it reports 26% for develop branch. It just dropped some months ago. Not sure what’s going on there ☹️ )