You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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):
The text was updated successfully, but these errors were encountered: