Skip to content

Since Feature Ignoring All Mutants #3234

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

Open
StevenAngel-ai opened this issue May 5, 2025 · 0 comments
Open

Since Feature Ignoring All Mutants #3234

StevenAngel-ai opened this issue May 5, 2025 · 0 comments
Labels
🐛 Bug Something isn't working

Comments

@StevenAngel-ai
Copy link

Describe the bug
When attempting to utilize the since feature to see if writing some tests killed any mutants, it ignored all mutants as "Mutant not changed compared to target commit"
From the docs, it would appear that the since feature should detect the code coverage change and re-run the affected mutants. "* For changes on test project files all mutants covered by tests in that file will be seen as changed."
Playing around further, I started making and committing changes in the file I was testing and it still ignored all mutants for the same reason. I can see in the output that Stryker sees that the files were changed. Unless I am missing something, it seems that the Since feature ignores all mutants.

Logs

logs.zip

Expected behavior
When running Stryker with --since:develop it should generate a report based only on mutants/test coverage that changed.

Desktop (please complete the following information):

  • OS: [Windows]
  • Type of project [NET]
  • Framework Version [8.0]
  • Stryker Version [4.5.1]
@StevenAngel-ai StevenAngel-ai added the 🐛 Bug Something isn't working label May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant