6 Commits

Author	SHA1	Message	Date
Miroslav Bajtoš	f9702b0ace	Use eslint with loopback config ... Drop jshint and jscs in favour of eslint. Fix style violations. While we are at this, reduce the max line length from 150 to 100.	2016-04-06 10:45:30 +02:00
Raymond Feng	34eb0e1a45	Disable application model test for karma	2015-07-28 08:39:58 -07:00
Miroslav Bajtoš	59ae90bb97	Run replication tests in the browser too	2015-03-06 14:50:16 +01:00
Miroslav Bajtoš	19519b038b	karma conf: prevent timeouts on Travis CI ... Increase the timeout values to prevent DISCONNECTED errors when running the tests on slow machines (e.g. Travis CI).	2015-03-03 09:47:49 +01:00
Miroslav Bajtoš	01d17e636a	test: run more tests in the browser ... Add two more test files to `test/karma.conf.js`: - test/loopback.test.js - test/model.application.test.js	2014-10-14 08:58:17 +02:00
Miroslav Bajtoš	50816ebbe3	Fix loopback in PhantomJS, fix karma tests ... - Move configuration of Karma unit-tests from `Gruntfile.js` to a standalone file (`test/karma.conf.js`). - Add a new Grunt task `karma:unit-ci` to run Karma unit-tests in PhantomJS and produce karma-xunit.xml file that can be consumed by the CI server. - Add grunt-mocha-test, configure it to run unit-tests. - Add `grunt test` task that runs both karma and mocha tests, detects Jenkins to produce XML output on CI server. - Modify the `test` script in `package.json` to run `grunt mocha-and-karma` (an alias for `grunt test`). The alias is required to trick `sl-ci-run` to run `npm test` instead of calling directly `mocha`. - Add `es5-shim` module to karma unit-tests in order to provide ES5-methods required by LoopBack. - Fix `mixin(source)` in lib/loopback.js to work in PhantomJS. `Object.getOwnPropertyDescriptor()` provided by `es5-shim` does not work in the same way as in Node.	2014-06-26 13:30:09 +02:00