Angular-cli: ng e2e -s or -w doesn't make any difference

Created on 21 Feb 2017 · 6Comments · Source: angular/angular-cli

What's the purpose of these flags? For me they don't do anything.
ng e2e always runs tests once and exits. Next time you have to rebuild everything again which takes forever. How can I make it to behave like ng serve, so it sits there and watches for changes?

Source

ctrl-brk

👍1

Most helpful comment

That's not the behavior I see. For me ng e2e runs just once and exits no matter what parameters I use.

ctrl-brk on 13 Mar 2017

👍2

All 6 comments

Still don't see a purpose for them in rc.1
How do I use it?

ctrl-brk on 4 Mar 2017

The --serve flag controls wether or not ng e2e will also serve your project. The default is true.

You can do ng e2e --no-serve to not serve. That's useful if you want use e2e on an already running server.

The --watch flag is passed on to the server with --serve is true. It defaults to false on ng e2e because it would be bad for live reload to kick in and reset your test while you're running ng e2e.

filipesilva on 13 Mar 2017

That's not the behavior I see. For me ng e2e runs just once and exits no matter what parameters I use.

ctrl-brk on 13 Mar 2017

👍2

ng e2e --no-serve is working fine for me

jculverwell on 7 Jun 2017

👍1

@ctrl-brk the server (same as ng serve) is what makes use of the --watch flag, the e2e test itself does not. An example of this behaviour would be that the browser auto reloads in the middle of an e2e test because you made a code change. This would break the e2e test.

I think the functionality you are expecting is the one requested in https://github.com/angular/angular-cli/issues/2861.

filipesilva on 12 Jun 2017

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