Stryker supports a number of plugins, which are listed below. You can also search npm for the stryker-plugin tag.
Don't worry about the reporters if you're just starting out. The needed plugins will be installed for you if you're following out quickstart.
Missing something? Feel free to create an issue or
- Jasmine (@stryker-mutator/jasmine-runner)
- Jest (@stryker-mutator/jest-runner)
- Karma (@stryker-mutator/karma-runner)
- Mocha (@stryker-mutator/mocha-runner)
- Web Component Tester (@stryker-mutator/wct-runner)
Stryker is test framework agnostic, however if you plugin hooks to the test framework you are using, it can significantly improve the performance
coverageAnalysis: 'perTest'. For more information about coverage analysis, see the stryker readme.
Stryker already has 4 reporters build in:
progress: Report progress during mutation testing.
dots: Report progress as dots during mutation testing.
clear-text: A clear text report at the end of the mutation testing phase.
event-recorder: Write all events to disk. Useful for debug purposes (default location: 'reports/mutation/events')
The actual mutating part of your code is done via a mutator plugin.
- TypeScript (@stryker-mutator/typescript-mutator)
Can mutate TypeScript files using the TypeScript parser.
- Vue (@stryker-mutator/vue-mutator)
A config writer is a plugin that can rewrite your stryker configuration during initialization. It is used by a few packages. We're thinking about deprecating it as it can lead to complicated setups with unexpected results.
<Your plugin here>
You can write your own plugins for Stryker. Interested? Come and have a chat at our gitter.