Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Setup @advanced tag for e2e test scenarios #559

Closed
slaweet opened this issue Mar 14, 2018 · 0 comments
Closed

Setup @advanced tag for e2e test scenarios #559

slaweet opened this issue Mar 14, 2018 · 0 comments
Assignees
@ginacontrino

Comments

@slaweet
Copy link
Contributor

slaweet commented Mar 14, 2018

Expected behaviour

There should be a way to exclude some e2e scenarios from running on each PR build and run them only on development or feature branch build.

A solution would be to have @advanced tag that would be filtered out by default, but enabled with npm run e2e-test -- --cucumberOpts.tags @advanced run e2e tests similarly we do with @testnet:
https://github.com/LiskHQ/lisk-hub/blob/c82683df85b2bc3277c697ebacff24463a8fed2c/Jenkinsfile#L142-L146

The first candidate for this tag is this scenario:
https://github.com/LiskHQ/lisk-hub/pull/458/files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ginacontrino ginacontrino

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@slaweet @ginacontrino