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

Run tests in parallel #121

Closed
tokunbo opened this issue Feb 21, 2013 · 3 comments
Closed

Run tests in parallel #121

tokunbo opened this issue Feb 21, 2013 · 3 comments

Comments

@tokunbo
Copy link

tokunbo commented Feb 21, 2013

Hello,

I have a fork that implements parallelism for behave. I would have submitted a pull-request, but my modifications break a few of the current options. Are there any plans to implement parallelism in the main branch? Have any opinions on my behave-parallel fork?

Thanks,

@jenisys
Copy link
Member

jenisys commented Feb 21, 2013

This would be interesting (and I will look into the changes and extension in your repository, but I probably will need some time).

QUICK FEEDBACK:
After looking at your README you apply parallelism at the scenario level.
This would at least break some of the feature files that I provided under issue.features/ directory. This is normally the case when I (mis-)use a Scenario for "Feature Test Setup" (like in "issue0111.feature") instead of using a Background. Therefore, the test writer probably needs a mechanism/control to mark a feature/scenario as safe for running in parallel or disabling parallelism (for example via a well-known tag: @not_parallel).

In addition, it would be nice if a user could decide if parallelism occurs at the Scenario or Feature level.

@tokunbo
Copy link
Author

tokunbo commented Feb 22, 2013

Awesome. I will work on adding those 2 features.

  • Allow choosing parallelism on feature-level or scenario-level
  • @notparallel tag to disable parallelism.

However, what does it mean when there are 10 scenarios, but only one has the @notparallel flag? Does it mean that scenario must go first/last? Or would the @notparallel tag only be valid on a feature element?

LATE EDIT: ....well, I'll just assume @notparallel is a feature only flag because I can't imagine what it would mean for an individual scenario. I'll close this issue now. Thanks for the input. 👍

@tokunbo tokunbo closed this as completed Feb 22, 2013
@tokunbo
Copy link
Author

tokunbo commented Feb 24, 2013

Features added.

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