Skip to content

[Feature Request] ng e2e --config-file parameter #976

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

Closed
PhilippSoehnlein opened this issue Jun 1, 2016 · 2 comments
Closed

[Feature Request] ng e2e --config-file parameter #976

PhilippSoehnlein opened this issue Jun 1, 2016 · 2 comments
Labels
effort1: easy (hours) P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@PhilippSoehnlein
Copy link

It looks like ng test has a --config-file parameter (see #966). A similar option for ng e2e would be cool.

For both commands my use case is a differentiation of tests if they run locally or on a CI server. Locally I would call ng e2e --config-file config/protractor-local.conf.js and the CI server would do a ng e2e --config-file config/protractor-ci.conf.js. Sure, you can build both cases into the same protractor.conf.js, but I'd like to have this separated. The same goes for ng test.

@filipesilva filipesilva added type: enhancement effort1: easy (hours) P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Jun 2, 2016
@filipesilva
Copy link
Contributor

This is now supported via the --config flag.

hansl added a commit that referenced this issue Jun 6, 2018
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
effort1: easy (hours) P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
2 participants