-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here (e.g. What to do if you already signed the CLAIndividual signers
Corporate signers
|
1 similar comment
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here (e.g. What to do if you already signed the CLAIndividual signers
Corporate signers
|
I signed it! |
CLAs look good, thanks! |
1 similar comment
CLAs look good, thanks! |
done() accept error as parameter in Jasmine 3 beforeEach() no longer allow in it() in Jasmine 3
resolved #4708 as well |
@@ -18,7 +18,7 @@ | |||
"blocking-proxy": "^1.0.0", | |||
"chalk": "^1.1.3", | |||
"glob": "^7.0.3", | |||
"jasmine": "2.8.0", | |||
"jasmine": "3.1.0", |
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.
Please also update package-lock.json
@@ -65,7 +65,6 @@ describe('local connect', function() { | |||
webdriver.getNewDriver(); | |||
} catch(e) { | |||
errorFound = true; | |||
expect(e.code).toBe(BrowserError.CODE); |
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.
why remove this?
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.
The purpose of this test is validate if error be thrown, not to verify the error code. I am not sure what is the root cause, but the exception don't have code property on my environment, the test will fail.
@@ -65,6 +65,6 @@ describe('the Protractor runner', function() { | |||
var runner = new Runner(config); | |||
runner.run().then(function() { | |||
done.fail('expected error when no custom framework is defined'); | |||
}, done); | |||
}, done()); |
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.
The "then" function receives a Function as parameter, passing done() to it will call "done" first and make the test always pass, won't it?
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.
This test is expecting exception thrown, so if error occurred, done(), test passed.
One big change in Jasmine 3 is done() accept one parameter now, if we pass done function here, done(e) will be called, Jasmine will fail the test. Alternative change here is
runner.run().then(function() {
done.fail('expected error when no custom framework is defined');
}, () => {return done();} );
Updated some of the spelling errors/ punctuation mistakes for clearer understanding.
Increase the scripts timeout
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
1 similar comment
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
Seems I messed up the PR... don't known why the saucelab related changes appear here. I will close this for now |
resolve #4788
Jamine 3 change the random default to true, however I want to keep protractor's default to false to avoid breaking changes.