Repository navigation
Flakey-ness in e2e tests with ng serve #4478
Description
Please provide us with the following information:
OS?
Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
All
Versions.
Please run
ng --version. If there's nothing outputted, please run in a Terminal:node --versionand paste the result here:
1.0.0-beta.29
Mention any other details that might be useful.
In order to run e2e tests, one has to run ng serve and ng e2e in parallel. Now, because ng serve does some preprocessing before serving (webpack build), it seems that protractor may timeout before the Angular app is served. This leads to flakey-ness on CI.
We (think we) have run into this here (which is a cli-generated app), but this issue will probably affect all projects using the cli. I think @filipesilva was running into something similar recently. We have tried several things, from increasing timeouts to other hacks, but a more robust solution is necessary.
Something like this helper might be useful for users or maybe another way is more appropriate. But it sounds like something that would benefit most users and it would be nice if the cli provided an easy way out.
cc @IgorMinar
Activity
filipesilva commentedon Feb 7, 2017
My usual solution to this is to not use
ng servefor e2e tests in CI. Instead I use a simpler static server (likelite-server), which is guaranteed to start up fast.Something like this (in terms of npm scripts):
I recognize the convenience of not having to manage processes to run e2e tests though. Maybe as part of #4256 a new flag could be introduced that would manage this on the CLI side.
Hypothetically something like
ng e2e --serve, defaulting to true.feat(e2e): use protractor api
feat(e2e): use protractor api
feat(e2e): use protractor api
feat(e2e): use protractor api
feat(e2e): use protractor api
feat(e2e): use protractor api
feat(e2e): use protractor api (#4527)
feat(e2e): use protractor api (angular#4527)
angular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
feat(e2e): use protractor api (angular#4527)