Do not run before_all/after_all hooks if no features are active #1113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Behave runs the before_all() and after_all() hooks, even if no features at all are to be executed (e.g. by filtering out all scenarios via tags).
This can be quite costly time-wise and annoying, as e.g. fixtures might be instantiated and configured in before_all/after_all.
This naïve patch fixes this by simply checking if any features are active before executing hooks.
I am open to suggestions if you think this approach has issues.