Integrate new test runner and test selector api's in stryker #53
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
… part of the path
…nal StrykerOptions
…when an actual test ran
…inetely and fixed no reporter being created
1. It is now possible to debug a stryker run (no more port in use) 2. Made sure timeout cannot occur after we received a message from the child process
|
There are still two issues, as far as I know:
EDIT: specnames are now printed but this does not seem right as every spec is printed instead of the ones that cover the Mutant |
simondel
added a commit
that referenced
this pull request
Mar 18, 2016
Integrate new test runner and test selector api's in stryker
|
We'll fix the coverage in a later version. |
sanderkoenders
pushed a commit
that referenced
this pull request
Jul 6, 2018
nicojs
pushed a commit
that referenced
this pull request
Jul 8, 2018
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.
Resolve #34
There is still work to be done, but i hope we can now start releasing a 0.1 release (beta)