Some minor improvements in the way spec tests were written #43
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
to ease creation of Parameterized tests based on specs + Used this method to automatically reference specs in SessionsTest
by using @RunWith(RestxSpecTestsRunner.class) & @FindSpecsIn I kept (in comment), the RestxSpecRule usage, in order to make the developper conscious of the *manual* way to executing spec tests
xhanin
added a commit
that referenced
this pull request
Aug 28, 2013
Some minor improvements in the way spec tests were written
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.
Not a big deal here, but discovered the existence of
RestxSpecTests&RestxSpecTestsRunner(to be honest, I started implementing my own
RestxSpecTestsRunnerbefore figuring it was already implemented :-D ... the funny part is I used thefindSpecsIn()method prototype exactly the same as you)