-
Notifications
You must be signed in to change notification settings - Fork 0
/
karma.conf.js
60 lines (51 loc) · 1.62 KB
/
karma.conf.js
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
module.exports = function ( karma ) {
process.env.PHANTOMJS_BIN = 'node_modules/karma-phantomjs-launcher/node_modules/.bin/phantomjs';
karma.set({
/**
* From where to look for files, starting with the location of this file.
*/
basePath: './',
/**
* Filled by the task `gulp karma-conf`
*/
files: [
],
frameworks: [ 'mocha', 'chai' ],
plugins: [ 'karma-mocha', 'karma-chai', 'karma-phantomjs-launcher' ],
/**
* How to report, by default.
*/
reporters: 'progress',
/**
* Show colors in output?
*/
colors: true,
/**
* On which port should the browser connect, on which port is the test runner
* operating, and what is the URL path for the browser to use.
*/
port: 9099,
runnerPort: 9100,
urlRoot: '/',
/**
* Disable file watching by default.
*/
autoWatch: false,
/**
* The list of browsers to launch to test on. This includes only "Firefox" by
* default, but other browser names include:
* Chrome, ChromeCanary, Firefox, Opera, Safari, PhantomJS
*
* Note that you can also use the executable name of the browser, like "chromium"
* or "firefox", but that these vary based on your operating system.
*
* You may also leave this blank and manually navigate your browser to
* http://localhost:9099/ when you're running tests. The window/tab can be left
* open and the tests will automatically occur there during the build. This has
* the aesthetic advantage of not launching a browser every time you save.
*/
browsers: [
'PhantomJS'
]
});
};