-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
Clean up and speed up cucumber test suite #544
Conversation
I'm going to go through the entire suite using |
Something that doesn't work is a bug, not a feature.
The step names mentioning 'default executable' and 'default feature' are unclear and therefore confusing. Better to write out the needed executable and feature in place.
These instructions should not be part of the test suite but go in CONTRIBUTING.md instead.
- Fix some typos and wording issues. - Add developer instructions that were in the feature files before.
The cucumber regexp will already ensure channel has a valid value.
The background section contained a step that was only relevant to some of the scenarios. Distribute it where relevant instead.
All the commit messages are clear and distinct. Makes archaeology easier and reviewing simpler. This attention to detail is a thing which keeps me around this project. Thank you so much for making this improvement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Travis has passed, I'd call this ready to go.
🎉 This should really help with getting the features passing on JRuby, since they now actually seem to finish in time! |
Summary
Remove slow and needless scenarios from our suite, and speed up some other slow scenarios.
Details
Motivation and Context
Our test suite takes a long time on CRuby, and an insanely long time on JRuby.
How Has This Been Tested?
Some specs were added, plus Travis.
Types of changes
Checklist: