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

Cucumber split by scenario and not feature #118

Open
juggy opened this issue Jan 11, 2022 · 1 comment
Open

Cucumber split by scenario and not feature #118

juggy opened this issue Jan 11, 2022 · 1 comment
Labels

Comments

@juggy
Copy link

juggy commented Jan 11, 2022

I created a report for my cucumber tests and it was broken down to the feature and not the scenario.

When running the tests in parallel, There seem to be a big difference between the fastest running node (14m) vs the slowest (35m). I think this is because some features are really big and some are not that much and since the splitting occurs on a feature level, it fails to split them correctly. That 35m one is actually a single feature.

Can you configure knapsack to generate a report and split cucumbers by scenario instead of features?

@ArturT
Copy link
Member

ArturT commented Jan 18, 2022

since the splitting occurs on a feature level, it fails to split them correctly

Tests are split based on the test file paths in the knapsack gem.

In the case of RSpec, it's possible to split based on test cases in knapsack_pro gem.

For Cucumber it's not possible yet. I'm not sure if Cucumber allows running individual test cases (a single scenario) from a given test file path like it does RSpec. In RSpec you can do bundle exec rspec spec/models/user_spec.rb:123 in order to run the test case from line 123. Do you know if Cucumber allows for something like that?

@ArturT ArturT added the feature label Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants