ci(aio): refactor the protractor config (#14248)
1. Use `jasmine` as framework instead of `jasmine2`. (Since angular/protractor@2bde92b, `jasmine2` is an alias for `jasmine`.) 2. Simplify the `chromeOptions` config by always setting. (If `process.env.CHROME_BIN` is not defined, `binary` will be ignored.)
This commit is contained in:
parent
0ba5bebf61
commit
fb91b2fe78
|
@ -11,11 +11,14 @@ exports.config = {
|
|||
'./e2e/**/*.e2e-spec.ts'
|
||||
],
|
||||
capabilities: {
|
||||
'browserName': 'chrome'
|
||||
browserName: 'chrome',
|
||||
chromeOptions: {
|
||||
binary: process.env.CHROME_BIN
|
||||
}
|
||||
},
|
||||
directConnect: true,
|
||||
baseUrl: 'http://localhost:4200/',
|
||||
framework: 'jasmine2',
|
||||
framework: 'jasmine',
|
||||
jasmineNodeOpts: {
|
||||
showColors: true,
|
||||
defaultTimeoutInterval: 30000,
|
||||
|
@ -31,9 +34,3 @@ exports.config = {
|
|||
jasmine.getEnv().addReporter(new SpecReporter());
|
||||
}
|
||||
};
|
||||
|
||||
if (process.env.TRAVIS) {
|
||||
exports.config.capabilities.chromeOptions = {
|
||||
binary: process.env.CHROME_BIN
|
||||
};
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue