feat(core): add support for checker plugins #2285
Merged
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
Implement a simple mutation testing process using mutation switching. BREAKING CHANGE: * Transpilers are no longer supported, please use build command instead * Custom mutators are no longer supported, Stryker now brings it's own mutator
* Remove test runner v1 stuff * Remove mutator plugin stuff * Remove test framework plugin stuff * Remove `SandboxPool` (was reimagined as `TestRunnerPool`) * Remove `MutantTestMatcher` (was reimagined as `findMutantTestCoverage`)
Add --concurrency (or -c) option which set the number of concurrent worker processes to be used by Stryker. A worker can be a checker process, or a test runner process. BREAKING CHANGE: * --maxConcurrentTestRunners is now deprecated. Plesae use `--concurrency` instead.
Require `init()` and `dispose()` of the new test runner api to return a `Promise<void>`.
Add support for Checker plugins. Checker plugins take the place of the transpiler in a way. When a checker plugin is configured, every mutant is checked before a test runner pickes it up. This will allow typescript type checking to take place. Since checking a mutant can take a long time (~2 sec/mutant on Stryker's core project), we use concurrent processes. These are entirely managed by Stryker core, plugin creators don't need to worry about this. The algoritm used to determine the number of checkers is `ceil(--concurrency / 2)`. This allows room for `floor(--concurrency / 2)` test runners. Once the check process is done, all check processes are closed and more test runner processes are spinned up to speed up the mutation testing process.
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.
Note: should be merged after #2269
Add support for Checker plugins. Checker plugins take the place of the transpiler in a way. When a checker plugin is configured, every mutant is checked before a test runner picks it up. This will allow typescript type checking to take place.
Since checking a mutant can take a long time (~2 sec/mutant on Stryker's core project), we use concurrent processes. These are entirely managed by Stryker core, plugin creators don't need to worry about this.
The algorithm used to determine the number of checkers is
ceil(--concurrency / 2). This allows room forfloor(--concurrency / 2)test runners. Once the check process is done, all check processes are closed and more test runner processes are spun up to speed up the mutation testing process.Add
--concurrency(or-c) option which set the number of concurrent worker processes to be used by Stryker. A worker can be a checker process or a test runner process.BREAKING CHANGE:
--maxConcurrentTestRunnersis now deprecated. Please use--concurrencyinstead.