Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Feature request: single e2e test run support #392

Closed
1 of 3 tasks
captaincaius opened this issue Oct 14, 2018 · 2 comments
Closed
1 of 3 tasks

Feature request: single e2e test run support #392

captaincaius opened this issue Oct 14, 2018 · 2 comments

Comments

@captaincaius
Copy link
Contributor

I'm submitting a...

  • Bug report
  • Feature request
  • Documentation issue or request

Current behavior

Generated apps can't run a single e2e spec from the commandline too easily.

Expected behavior

You can run a single spec without hacking protractor conf manually

Is there any interest in supporting this?

@sinedied
Copy link
Member

Since the tests are written in jasmine you can always prefix the test or test suite by f (ie fdescribe or fit), or from the CLI you can use the --specs option it seems: angular/protractor#164

Using angular-cli e2e command, it seems you can only specify a --suite and not a single test: https://github.com/angular/angular-cli/wiki/e2e

@captaincaius
Copy link
Contributor Author

well the way I've been doing it is that I keep a protractor-single.conf, a protractor.conf, and a protractor-common.conf - it's not pretty, but it avoids the risk of someone accidentally missing a PR with "fdescribe" or something similar on it.

I've been keeping protractor-single in .gitignore, but I think nowadays it can be done with a commandline parameter or an environment variable instead of manually hacking the specs in -single.conf.

But ok if you think it's yagni, we can close this ;).

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants