Configure default spec framework and test framework #67
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
added 15 commits
August 29, 2015 21:42
In preparation for a configurable spec framework and to refactor the SourceInfo specs. SourceInfo relied too much on state and order of operations. Refactor ::minitestRegExp() and ::isMiniTest() to be independent of order of operations.
* Split off ::extractMinitestRegExp() from ::minitestRegExp() * Refactor ::fileAnalysis() more
moxley
changed the title
moxley
added a commit
that referenced
this pull request
Aug 30, 2015
Configure default spec framework and test framework
|
Fixes #57 |
This was referenced Aug 30, 2015
Closed
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.
What
Configuration setting for default spec framework and test framework, so that ruby-test doesn't guess whether it's RSpec or Minitest or Test::Unit.