-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stryker with Mocha / Typescript results in different mutation score every run #1109
Comments
@csimko I can also reproduce this on my machine. The score seems to be more consistent if I don't test in parallel ( The transpiler errors seem to always be the same, so the issue really seems to be in your tests. What kind of application is it? What system resources (files outside of src and test, network ports on your system, etc) does it use? |
I am seeing consistent runs on Linux with a score of 21,74%. Seems to be related to Windows indeed. |
Thanks for testing it @archcry! |
@Archcry, @simondel when I was making PR and testing on linux i also had inconsistent results (probably caused by memory limit) [travis tests it perfectly :/], but on windows it is not consistent at all. [Simondel PR is waiting for you :)] |
I'm closing this issue for now. If you need any help from us, let us know! |
Summary
When running stryker run with mocha and typescript it succeeds. However the issue is that on every subsequent run the score is different. No file manipulation is present, no changes to source are made during runs.
Reproduction
Please checkout the following branch:
https://github.com/ChannelApe/channelape-typescript-web-service-sdk/tree/feature/channelape-actions-controller-and-sqs-functions
Run npm i
Run npm run mutate
stryker_first_run.log
stryker_second_run.log
You will note that stryker succeeds. Make note of the mutation score
Run npm run mutate again
Now you will see that the score has changed. You may repeat this as often as you like, the score is different each time.
Stryker config
Stryker environment
Your Environment
stryker_first_run.log
stryker_second_run.log
The text was updated successfully, but these errors were encountered: