Skip to content

feat(e2e): Added --config-file flag to e2e command #1054

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
wants to merge 1 commit into from
Closed

feat(e2e): Added --config-file flag to e2e command #1054

wants to merge 1 commit into from

Conversation

marc-sensenich
Copy link
Contributor

This change will allow for a user to pass in a different config-file for e2e testing through the --config-file flag

Fix #976

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

@googlebot
Copy link

CLAs look good, thanks!

@Brocco
Copy link
Contributor

Brocco commented Oct 14, 2016

Please update this PR after rebasing on latest master

@chompy18
Copy link

chompy18 commented Nov 2, 2016

Hi,
Any update on this feature merge?
This could really help me with running different suites at different scenarios...

@marc-sensenich
Copy link
Contributor Author

I've got to dive back into it. I'm gonna rebase it this evening and update it

Sent from my iPhone

On Nov 2, 2016, at 06:28, chompy18 [email protected] wrote:

Hi,
Any update on this feature merge?
This could really help me with running different suites at different scenarios...


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@parminderkaur
Copy link

Any update on when this will be merged into master?

Allow for a user to use the optional --config flag to specify the usage of
a different configuration file for Protractor end-to-end testing. This
configuration file is first defined in angular-cli.json and refrenced by
the key defined
@marc-sensenich
Copy link
Contributor Author

@filipesilva removed that change and resolved the lint CI error

On Mon, Nov 21, 2016 at 8:53 AM, Filipe Silva [email protected]
wrote:

@filipesilva requested changes on this pull request.

LGTM except for that extra change in schema.json and the lint CI error:

packages/angular-cli/tasks/e2e.ts[14, 1]: trailing whitespace

Can you fix those please?

In packages/angular-cli/lib/config/schema.json
#1054 (review)
:

@@ -112,7 +112,7 @@
"type": "string"
}
},

  •      "additionalProperties": false
    
  •      "additionalProperties": true
    

Can you remove this change?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1054 (review),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ9WvT9GFdkm7vA2MdmmmlB5T3mOCgTJks5rAaJXgaJpZM4Iyi5Q
.

Marc Sensenich

email: [email protected]

Copy link
Contributor

@hansl hansl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry to come in late but I'm going through the PR queue now.

The idea here would be to have any config files in the angular-cli.json, correct? If so, could you update the README?

Alternatively, I could see this flag specify a file instead of a key in the configuration. What do you think?

@@ -19,5 +19,6 @@ export default function() {
.then(() => _runServeAndE2e())
.then(() => _runServeAndE2e('--prod'))
.then(() => _runServeAndE2e('--aot'))
.then(() => _runServeAndE2e('--aot', '--prod'));
.then(() => _runServeAndE2e('--aot', '--prod'))
.then(() => _runServeAndE2e('--config', 'config'));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you create an e2e that actually uses another config instead of the same default one?

@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 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature Request] ng e2e --config-file parameter
7 participants