Initial commit with .hgignore
First functionality commit, contains a PhantomRunner.java which can scan javascript test files but cannot yet do anything with those
JUnit Description parsing with QUnit tests
Adds proper Notifier hooks for tests so it knows when test is ran
Work on actually executing the QUnit tests on PhantomJS. Doesn't work yet but getting there.
Decided that QUnit is a bad choice since it works purely on the state of DOM (which is just bad). Jasmine looks a lot more promising in all possible ways and will integrate that as the first functional test framework. Unfortunately this change made me to revert a lot of code and that work is still work in progress.
Fixes Jasmine based problems at Java side. Need some work still to tie the parsed objects to JUnit Descriptions and after that it's the Javascript side of things to do.
Lots of refactoring, provides javascript side of things a way to initialize the full js test file at once and then run each test separately. Also improves the separation of concerns and makes the core less dependent of Jasmine
Some refactorings, starts work on examining the Jasmine API
First actually working version of Jasmine integration. Currently for some reason Maven doesn't see the tests (but it does run them)
Moves interpreter library paths away from the test configuration - interpreters know their libraries and can provide those themselves
Provides a way to add external libraries to web pages before tests are ran. Also makes it possible to override the javascript test library files in case they get old.
Sets UTF-8 as the build charset - shame on me for not placing this here earlier...
Opens a branch for implementing jetty-integration into the JUnit runner so that PhantomJS can be ran completely in the client mode. This is done because available Javascript module loading mechanisms expect a server to exist so that they can load data from there (RequireJS and Jingo for example). In the current architecture this prevents these libraries from working correctly and causes a lot of other problems too.

--HG--
branch : jetty-integration
Changes the architecture into such that Java starts a Jetty and PhantomJS talks to it via websockets. Practically now at the same situation as at commit #a041a66c914b but with inverse responsibilities.

--HG--
branch : jetty-integration
Work on making require.js to work, unfortunately this caused the fact that in order for it to work it needs a proper html file loaded from server. Thus started implementing a mechanism which will generate a HTML file for tests - this work is still wip and currently everything is fubar

--HG--
branch : jetty-integration
Fixes almost all of the remaining problems. Only two problems remain: 1) Maven doesn't see the tests for some reason 2) In order for all of this to work I had to fork the jsoup library - patch files are waiting to be pushed as pull requests into github

--HG--
branch : jetty-integration
Fixes the maven bug

--HG--
branch : jetty-integration
Some minor tweaks to JUnit notifier calls, adds failMessage to response JSON from jasmine-runner and wraps the jasmine test runs into a specific JUnit test which ensures that fails are evaluated correctly

--HG--
branch : jetty-integration
Adds a bit more assertions to the PhantomRunnerTest

--HG--
branch : jetty-integration