Added a new argument to the MultiNodeTestRunner to filter specs #1737
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
|
I know @GraemeBradbury would like this :) |
Aaronontheweb
added a commit
that referenced
this pull request
Mar 1, 2016
Added a new argument to the MultiNodeTestRunner to filter specs
This was referenced Apr 6, 2016
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.
While I was testing the RemoteGatePiercingSpec I found it annoying that I need to run all specs in the assembly and therefore I have created another argument
-Dmultinode.specwhich takes a string and only executes specs that contain the given name.It checks the method name that is marked with the
MultiNodeFactattribute.For example: