The Great Testing Refactor

[qpfiffer]

Tests need to be split up. We need tests for the frontend. This ticket is for:

• Where do we put tests?
• The testing binary needs to have everything split up logically to test components
• Where do the frontend tests live and what do we write them in?

[Hamcha]

Related to #126 I still want duration in tests if possible, it'll make it easier to find bottlenecks without bothering the buildbot.

My proposal is to still make them a different folder, although a Golang-style "<something>_test.[c|h]" (as @kyleterry proposed on IRC) might be cool, although I fear cluttering of the source/include folder.

As currently decided with @kyleterry, Frontend tests will come in two flavors: binding tests (via go test) and api tests (via shell→curl). We're using #127 for the details on those.

[colby]

I personally would like to see tests in project root, under test/ or spec/, from there perhaps it could be test/frontend/testserver.c and/or spec/backend/findkey.c, roughly.

I am not familiar with C or Go testing, only Ruby, which would be useless to pull in for testing.

[Hamcha]

I like the test subfolder idea!

[kyleterry]

Me too!