Refactor normalize test suite usage #6
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There is a quite widespread convention that the default Rake task runs the test suite (Travis CI uses it for example). Running the Cucumber features using running 'cucumber' (resp. 'bundle exec cucumber') is still possible. Also more Rake tasks could be added for convenience, and the debug scenarios cold be run using 'rake cucumber:debug' for example.
gonzalo-bulnes
changed the title
|
See #5 (comment):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As a Ruby developer new to this project
In order to get started quickly
And know which part of the test suite is intended to be run daily
When I run
rakeThen I want to see the entire test suite output
See #5