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.

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

Common Features should be run first #15

Open
vrutkovs opened this issue Apr 30, 2015 · 1 comment
Open

Common Features should be run first #15

vrutkovs opened this issue Apr 30, 2015 · 1 comment
Milestone

Comments

@vrutkovs
Copy link
Member

Starting tests if general features don't pass is pointless, currently those features are queued at the end.

We should either start behave twice (once for common Docker features and then other tests) or make sure common-features are being run first

@rwngwn
Copy link
Contributor

rwngwn commented May 4, 2015

I don't think that running behave multiple time is a good idea. Maybe we should introduce some dependency decorator and then just skip rest of tests using something like

for scenario in feature.scenarios:
    scenario.mark_skipped  

Also test steps/features ordering seems for me more like behave stuff that should be fixed in upstream and reused in this framework rather than implemented here in a hacky way.

@vrutkovs vrutkovs modified the milestone: 0.1 May 19, 2015
@vrutkovs vrutkovs modified the milestones: 0.2, 0.1 Jul 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants