Add Jasmine unit testing framework

[localjo]

I added and configured the Jasmine unit testing framework which can be used to start writing some unit tests. Before writing any really useful tests, the Chrome API will probably need to be mocked. There's just enough in tests/spec/chrome.helper.js that the Jasmine framework can run without any errors.

[localjo]

There is a decent write-up about testing Chrome extensions with Jasmine here: http://blog.robertosoares.me/blog/2012/08/08/testing-chrome-extensions-with-jasmine/

[localjo]

@pushred for now I've got the unit testing framework configured and running with Grunt so that we can easily write tests for stuff with minimal friction. I want to merge this branch into the master for now and then open up some new issues to discuss things that need to be tested.

Off the top of my head, one thing that should probably be tested is that we're checking for the right x-powered-by header, since I've already committed that part of the code with the wrong string twice. 🙈

[pushred]

Would be nice to replace this with that header test you mentioned, since you're committing, merging, etc. This way you'd actually be testing your own API rather than the assertion library. That doesn't really count

[localjo]

I added a test to check to make sure getJsonResource() checks the x-powered-by header against the string Solidus (versus another string, like Express).

Something else seems to be preventing Jasmine/PhantomJS from completing tests in general. I think it might have to do with socket.io, but I'm still trying to track down the problem.

[localjo]

\o/

[pushred]

👏