-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng e2e #1017
Labels
effort1: easy (hours)
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
type: bug/fix
Comments
filipesilva
added
type: bug/fix
effort1: easy (hours)
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
labels
Jun 6, 2016
+1 to this |
filipesilva
pushed a commit
that referenced
this issue
Jun 9, 2016
filipesilva
pushed a commit
that referenced
this issue
Jun 9, 2016
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
effort1: easy (hours)
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
type: bug/fix
Hi all! Thanks for your hard work on angular-cli. It seems that
ng e2e
returns a status code of0
even when it fails. This makes continuous integration painful. I have purposefully demonstrated a scenario below where my tests fail, and I expected angular-cli to be returning1
.If I run the underlying protractor configuration, I get the result I expected:
Issue checklist:
OS X Yosemite (10.10.5)
ng --version
do on your code? etc.
No changes. Generated using CLI.
more information.
See above.
The text was updated successfully, but these errors were encountered: