-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add support for jasmine-spec-reporter (displayStacktrace: true) #70
Changes from 2 commits
ea80f2c
9d446b7
1d2d790
f9229b5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
'use strict'; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd remove this file unless we need it since (we don't have an integration test that actually uses it) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Cool... wasn't sure if you wanted a repeatable conf for the future [WOOSH SOUND]. The answer is no :) It's gone. |
||
|
||
var JOB_NUMBER = (process.env.TRAVIS_JOB_NUMBER || '') | ||
var JOB_NAME = 'Flake' + JOB_NUMBER | ||
|
||
exports.config = { | ||
specs: [ | ||
'../flakey-test.js', | ||
'../passing-test.js' | ||
], | ||
|
||
capabilities: { | ||
browserName: 'chrome', | ||
name: JOB_NAME, | ||
shardTestFiles: false, | ||
maxInstances: 2, | ||
'tunnel-identifier': JOB_NUMBER | ||
}, | ||
|
||
sauceUser: process.env.SAUCE_USERNAME, | ||
sauceKey: process.env.SAUCE_ACCESS_KEY, | ||
|
||
baseUrl: 'http://localhost:3000/', | ||
|
||
framework: 'jasmine2', | ||
|
||
allScriptsTimeout: 10000, | ||
|
||
getPageTimeout: 3000, | ||
|
||
jasmineNodeOpts: { | ||
defaultTimeoutInterval: 5000, | ||
print: function() {} // remove dot reporter | ||
}, | ||
|
||
onPrepare: function () { | ||
// let protractor know it doesn't need to look for angular on the page | ||
browser.ignoreSynchronization = true; | ||
|
||
// make reports mo' pretty | ||
var SpecReporter = require('jasmine-spec-reporter').SpecReporter; | ||
jasmine.getEnv().addReporter( | ||
new SpecReporter({ | ||
spec: { | ||
displayStacktrace: true | ||
} | ||
}) | ||
); | ||
} | ||
}; | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
[08:04:24] I/launcher - Running 1 instances of WebDriver | ||
[08:04:24] I/direct - Using ChromeDriver directly... | ||
Jasmine started | ||
|
||
a flakey integration test | ||
✗ fails, in a horribly consistent manner | ||
- Expected false to be truthy. | ||
at UserContext.<anonymous> (/tests/flakey.test.js:7:39) | ||
at node_modules/jasminewd2/index.js:112:25 | ||
at new ManagedPromise (node_modules/selenium-webdriver/lib/promise.js:1067:7) | ||
at ControlFlow.promise (node_modules/selenium-webdriver/lib/promise.js:2396:12) | ||
at schedulerExecute (node_modules/jasminewd2/index.js:95:18) | ||
at TaskQueue.execute_ (node_modules/selenium-webdriver/lib/promise.js:2970:14) | ||
at TaskQueue.executeNext_ (node_modules/selenium-webdriver/lib/promise.js:2953:27) | ||
at asyncRun (node_modules/selenium-webdriver/lib/promise.js:2813:27) | ||
at node_modules/selenium-webdriver/lib/promise.js:676:7 | ||
|
||
A test that passes | ||
✓ passes | ||
|
||
************************************************** | ||
* Failures * | ||
************************************************** | ||
|
||
1) a flakey integration test fails, in a horribly consistent manner | ||
- Expected false to be truthy. | ||
|
||
Executed 2 of 2 specs (1 FAILED) in 0.742 sec. | ||
[08:04:26] I/launcher - 0 instance(s) of WebDriver still running | ||
[08:04:26] I/launcher - chrome #01 failed 1 test(s) | ||
[08:04:26] I/launcher - overall: 1 failed spec(s) | ||
[08:04:26] E/launcher - Process exited with error code 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this dependency actually needed? I'm fine with omitting it since we have generated the static test output
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not now that the conf using it is gone