-
Notifications
You must be signed in to change notification settings - Fork 12k
Do not run e2e if build fails with "ng e2e --serve=true" #7567
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
Comments
This sounds like a bug actually. I agree we shouldn't even try to run the e2e if the build failed. |
@filipesilva : I'd like to work on this defect and I identified the problematic part. Can you do me a small favor and tell me how can I test these changes locally? If I am on right track, these are the files I need to change And most likely also change the way the promise resolves in I'm just having trouble figuring out how do I run my changes locally. Any help would be appreciated. TIA |
@adityaparab you should take a look here https://github.com/angular/angular-cli#development-hints-for-working-on-angular-cli |
@maxime1992 : Sweet! Thanks mate! That indeed is helpful.. I will submit a PR soon. :) |
when ng e2e --serve=true is run and the build is not successful e2e task should not be run previously the e2e task was run even if build was a failure which will obviously result in failure of test cases now if errors are detected in build the e2e task will not be run update docs as well to reflect this behaviour Closes #7567
when ng e2e --serve=true is run and the build is not successful e2e task should not be run previously the e2e task was run even if build was a failure which will obviously result in failure of test cases now if errors are detected in build the e2e task will not be run update docs as well to reflect this behaviour Closes #7567
when ng e2e --serve=true is run and the build is not successful e2e task should not be run previously the e2e task was run even if build was a failure which will obviously result in failure of test cases now if errors are detected in build the e2e task will not be run update docs as well to reflect this behaviour Closes #7567
when ng e2e --serve=true is run and the build is not successful e2e task should not be run previously the e2e task was run even if build was a failure which will obviously result in failure of test cases now if errors are detected in build the e2e task will not be run update docs as well to reflect this behaviour Closes angular#7567
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. |
Bug Report or Feature Request (mark with an
x
)Versions.
Repro steps.
With an application that does not build, if you run
ng e2e
, it will build it, the build will be shown as failed, but the e2e tests will be run nevertheless, which doesn't make any sense.Desired functionality.
Simply fail
ng e2e
as soon as we detect the application can't be built.The text was updated successfully, but these errors were encountered: