Use karma, add Coveralls integration.

[ChALkeR]

This gives us crude coverage analysis.
It's based on a single file atm (lib/qt.js), that has to be fixed later.
Another related problem is that it also analyzes the bundled uglify-js code.

There are several ways of fixing that, but that could be done in follow-up PRs.

This (sort of) fixes #40.

[ChALkeR]

/cc @qmlweb/collaborators I want this reviewed.

It doesn't give us detailed analysis yet (that will follow), but it does give us an overall percentage.
Some more info is available in the coverage folder after running npm test locally.

[henrikrudstrom]

That worked much better, had trouble getting gulp-jasmine-phantom to work, and it didnt seem so active.

[ChALkeR]

@henrikrudstrom Should I treat this as a review? =)

[ChALkeR]

Note that internally this still uses the same testing framework, Jasmine.

[henrikrudstrom]

if you want. Im no expert on testing, but this works out of the box and seems much more active, only thing i miss is the green text saying which tests passed...

[ChALkeR]

No objections raised, merging.
This is just toolchain change and does not break (or touch) the actual code, so I'm confident in this.

[ChALkeR]

@henrikrudstrom

only thing i miss is the green text saying which tests passed...

If it did that, then when there will be many tests, it would be noisy. It outputs only tests that fail =).