dungeonsoffear - 2016-03-02

I've been working on adding test coverage to the project. So far, this has been pretty boring and unmotivating, but I've done a lot. First, I shored up my configuration switching, so now I can switch between production, debug, and test environments. This will help with the deployment strategy (which should be simple given the structure of the program). I also added the unit testing framework, PHP unit, and converted some of the database bootstrapping code to work as both a command line tool and an importable function. Tonight I finally set up xDebug so that I can more quickly diagnose problems. Turns out, xDebug, although not flashy, does exactly what I need it to do, and I'm using Netbeans as my debugging client. Usually IDE's freak me out but Netbeans let me create a PHP project and store its metadata elsewhere, so it was very unintrusive. I've also documented functions and refactored code where needed, which will continue.

While I was feeling frustrated with my tests, I instead switched mental gears and took the attitude that this is tough work but important to the overall reliability of the app. I should be proud of this work, because in the long run reliability issues can make or break a software product of any kind.

I've tested invite.php and utils.php, so that leaves:
- dungeon
- game_player
- game_room
- player
- auth
- settings

Then its back to room creation.

6 Hours