Angular-cli: ng e2e doesn't use existing ng serve session

Created on 11 Nov 2016  Â·  8Comments  Â·  Source: angular/angular-cli

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
mac sierra

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
angular-cli: 1.0.0-beta.19-3
node: 7.0.0
os: darwin x64

Current behavior
opens a new session everytime i test, which is very slow

Expected behavior
expects to use existing sessions

Minimal reproduction of the problem with instructions
just try to run ng serve, then run ng e2e

What is the motivation / use case for changing the behavior?
test faster

Mention any other details that might be useful.


Thanks! We'll be in touch soon.

Most helpful comment

You can actually do that with now with ng e2e --serve=false ( see https://github.com/angular/angular-cli/wiki/e2e for details).

All 8 comments

how's the resolve coming along?

The way Protractor (the e2e library) works is by opening a new browser window and running your commands in it.

This is how it should work, it shouldn't use your existing browser window. If it did, you wouldn't be testing a full journey through your app.

yes that i can understand

however, it's taking too long for every e2e test, may I know how can I
speed it up faster?

On 22 November 2016 at 02:51, Filipe Silva [email protected] wrote:

Closed #3111 https://github.com/angular/angular-cli/issues/3111.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/3111#event-867038639, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AERKhgyfZO5JHsMWB5cst7gIFay7hAWKks5rAegmgaJpZM4Kvcup
.

e2e is slow overall, but maybe we can find some tips in https://github.com/angular/protractor

@filipesilva He's not talking about another browser session, he's talking about the server. So, ng serve will serve up your app... and then ng e2e will use the already served up app with a new browser session each time you run it.

@JeremyIglehart This would speed e2e development up a lot, as the project doesn't have to recompile every time is called ng e2e

You can actually do that with now with ng e2e --serve=false ( see https://github.com/angular/angular-cli/wiki/e2e for details).

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._

Was this page helpful?
0 / 5 - 0 ratings

Related issues

5amfung picture 5amfung  Â·  3Comments

naveedahmed1 picture naveedahmed1  Â·  3Comments

JanStureNielsen picture JanStureNielsen  Â·  3Comments

rajjejosefsson picture rajjejosefsson  Â·  3Comments

rwillmer picture rwillmer  Â·  3Comments