I would like to see first class stryker-mutator support in cypress. Right now it is possible to run stryker-mutator and cypress together but there are some major issues. First it takes an extreme long time to finish because its only possible to run if you tell stryker the cypress run command and stryker will call it for every mutation. So runtime goes up really fast. Second stryker will not get any coverage analysis data that will also play in to runtime. And the last thing i could see is it does not really get the test report. So it will tell you all mutations have survived.
Why is this needed?
Because of the way cypress works its needed to get some first class api support for stryker so it can hook in to livecycles. Like dont start the runner for every mutation anew but hold one runner instance and run it again and again for every code mutation. Also it would give way more insights for stryker to run faster and actually capture the results from cypress.
What would you like?
I would like to see first class stryker-mutator support in cypress. Right now it is possible to run stryker-mutator and cypress together but there are some major issues. First it takes an extreme long time to finish because its only possible to run if you tell stryker the cypress run command and stryker will call it for every mutation. So runtime goes up really fast. Second stryker will not get any coverage analysis data that will also play in to runtime. And the last thing i could see is it does not really get the test report. So it will tell you all mutations have survived.
Why is this needed?
Because of the way cypress works its needed to get some first class api support for stryker so it can hook in to livecycles. Like dont start the runner for every mutation anew but hold one runner instance and run it again and again for every code mutation. Also it would give way more insights for stryker to run faster and actually capture the results from cypress.
Here is an link to the homepage: https://stryker-mutator.io/