Skip to content
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

Support Stryker-Mutator #16299

Open
ckruppe opened this issue May 2, 2021 · 2 comments
Open

Support Stryker-Mutator #16299

ckruppe opened this issue May 2, 2021 · 2 comments
Labels
stage: proposal 💡 No work has been done of this issue type: feature New feature that does not currently exist

Comments

@ckruppe
Copy link

ckruppe commented May 2, 2021

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/

@bahmutov
Copy link
Contributor

bahmutov commented May 2, 2021

Yes, it is something I am interested in, will experiment

@bahmutov bahmutov self-assigned this May 2, 2021
@jennifer-shehane jennifer-shehane added stage: proposal 💡 No work has been done of this issue type: feature New feature that does not currently exist labels May 3, 2021
@kght6123-work
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stage: proposal 💡 No work has been done of this issue type: feature New feature that does not currently exist
Projects
None yet
Development

No branches or pull requests

4 participants