Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

move test_util out of q, rework due to es6 #5036

Merged
merged 23 commits into from
Nov 28, 2018
Merged

move test_util out of q, rework due to es6 #5036

merged 23 commits into from
Nov 28, 2018

Conversation

CrispusDH
Copy link
Contributor

@CrispusDH CrispusDH commented Nov 13, 2018

  • rework test_util
  • check passed tests locally
  • check correct behavior if some test failed
  • update node version in CircleCI to LTS (tests were failed on previous v8)
  • change octaral literals to something different

I don't know how to fix it:

Octal literals are not allowed in strict mode
console.log('\n>>> \033[1;32mpass\033[0m');

@CrispusDH
Copy link
Contributor Author

@cnishina , could you take a look at this PR, please

@cnishina
Copy link
Member

Let's leave the octal literals as is. This should be blocked by #5038. In #5038, the PR turns on more of the error tests.

@CrispusDH
Copy link
Contributor Author

Reference #4995

Copy link
Member

@cnishina cnishina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's try to escape the octal per the stackoverflow comment. My guess is because we moved to ES6 syntax, it automatically applied "use strict" on us.

scripts/test/test_util.js Show resolved Hide resolved
scripts/test/test_util.js Show resolved Hide resolved
@CrispusDH
Copy link
Contributor Author

It fix change octal to plain text. So, in console is just >>> \033[1;32mpass\033[0m

@CrispusDH
Copy link
Contributor Author

CrispusDH commented Nov 17, 2018

@cnishina , I suggest change:

  1. \n>>> \033[1;31mfail: ' + err.toString() + '\033[0m, that produce just "pass" to \n>>> test was passed
  2. \n>>> \033[1;31mfail: ' + err.toString() + '\033[0m, change to \n>>> test was failed. Error: ${error}

@googlebot
Copy link

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 cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

1 similar comment
@googlebot
Copy link

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 cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

1 similar comment
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@googlebot
Copy link

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 cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@cnishina
Copy link
Member

cnishina commented Nov 27, 2018

So here's how I would fix up the PR.... #5058

The octal is problematic but we are not required to update everything. Leaving that last section as is in test_util is fine. The bigger concern is to remove q. I made some changes to move this PR along.

@cnishina cnishina added cla: yes and removed cla: no labels Nov 27, 2018
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

1 similar comment
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@googlebot
Copy link

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 cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@googlebot
Copy link

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 cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@cnishina cnishina added cla: yes and removed cla: no labels Nov 27, 2018
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

1 similar comment
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@cnishina cnishina dismissed their stale review November 28, 2018 00:00

Also helped out with this, so I am not a good reviewer.

@cnishina cnishina merged commit ee73f2d into angular:selenium4 Nov 28, 2018
@CrispusDH CrispusDH deleted the test_util branch November 28, 2018 06:18
cnishina pushed a commit to cnishina/protractor that referenced this pull request Dec 19, 2018
cnishina pushed a commit to cnishina/protractor that referenced this pull request Mar 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants