Commit Graph

14 Commits

Author SHA1 Message Date
Marc Jansen 8c487d3036 Allow configuration of the test reporter
The reporter for the standard tests is still 'spec'; the one for the
gathering of code coverage is set to 'dot' to not clutter the output
of the logfile on travis.
2016-03-08 11:26:00 +01:00
Tim Schaub 6f525bfd2e Use new package name 2016-01-28 09:26:23 -07:00
Tim Schaub 38d0e98ff5 Whitespace 2016-01-11 18:56:05 -08:00
Tim Schaub 1d65bab158 Dangling commas 2016-01-11 18:56:05 -08:00
Andreas Hocevar a58f66a9a9 Fix usage of mocha-phantomjs-core after update 2015-11-06 20:34:30 +01:00
Tim Schaub 98c9b0eb39 Update phantomjs and use mocha-phantomjs-core 2015-11-01 01:18:59 -07:00
Tim Schaub 4549d2f7a8 Try multiple ports 2015-07-09 10:49:24 -06:00
tsauerwein 8e0c21eb58 Add test-suite using SlimerJS 2015-04-04 17:30:38 +02:00
Marc Jansen 6a9c8f36f7 Refactor tasks/test.js to be more modular.
This way the main functionality of the script can be reused in the
tasks/test-coverage.js script, which has to run the testsuite as well.
2015-04-02 09:13:17 +02:00
Bart van den Eijnden 7c9795ba35 Integrate istanbul for test coverage 2015-04-02 08:57:53 +02:00
Andreas Hocevar 9462c2148d Listen on localhost to avoid phantomjs browsing 0.0.0.0 2015-03-17 14:39:00 +01:00
Tim Schaub 33b68123ac Add jshint config for tasks and remove lint 2014-08-18 17:22:57 -06:00
Tim Schaub 8a3f1a8f34 Add mocha and mocha-phantomjs as dev dependencies 2014-07-06 11:40:08 -06:00
Tim Schaub b452e04e08 Add a task to run the tests once with PhantomJS
The test.js task starts the development server and runs the tests in PhantomJS.  As mentioned in the readme, when running the tests continuously during development, it is more convenient to start the dev server and visit the root of the test directory in your browser.

Later we can bring in Karma to drive PhantomJS and other browsers, but this simple "run once" task is useful for the CI job.
2014-07-05 19:42:30 -04:00