-
Notifications
You must be signed in to change notification settings - Fork 12k
ng e2e does not start a webserver #4042
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 is intended behaviour, This was chosen because there are multiple ways in which you might want to test your project. For instance, you might need to test the latest build, that was done via My recommendation for running e2e on a CI environment is to add this npm script:
This script relies on https://github.com/kimmobrunfeldt/concurrently to coordinate processes and the fact that starting a lightweight webserver is always faster than starting protractor. You might want to omit |
Thanks for the suggestion :) |
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. |
OS?
OS X El Capitan
Versions.
angular-cli: 1.0.0-beta.25.5
node: 6.7.0
os: darwin x64
@angular/common: 2.4.3
@angular/compiler: 2.4.3
@angular/core: 2.4.3
@angular/forms: 2.4.3
@angular/http: 2.4.3
@angular/platform-browser: 2.4.3
@angular/platform-browser-dynamic: 2.4.3
@angular/router: 3.4.3
@angular/material: 2.0.0-beta.1
Repro steps.
Running
ng e2e
fails because the webserver is never started.The log given by the failure.
Mention any other details that might be useful.
If this is expected behaviour, there should be a way to start a dev server and attach a callback to it so that we manually trigger the integration tests once the dev server is started.
The text was updated successfully, but these errors were encountered: