Go Tests

[lukevers]

Currently we use Travis-CI for making sure everything is good, but we also can run tests! Our .travis.yml file is already set up to run go test, but right now there are no go test files in master.

• api.go
• cache.go
• captcha.go
• config.go
• database.go
• doc.go
• import.go
• nodeatlas.go
• nodes.go
• smtp.go
• static.go
• verify.go
• web.go

[lukevers]

I accidentally created this branch from master an extra commit behind, so I merged master into f.go_tests because it contained the important .travis.yml file for testing!

[alexander-bauer]

One of the difficulties with unit testing NodeAtlas is that it is heavily dependent on a running database, and if there is no such database existent and initialized prior to running the tests, then they fail, but Go provides no way to initialize objects prior to running tests. It is very inconvenient.

However, if we could try to build some infrastructure to allow us to initialize a database (or wait for a database to be initialized) if we included a function call at the start of each function that relies on the database. Then we would need to be certain it is cleaned up, but I'm not sure how to do that.