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
run the tests again and check if the test suite “kills” the mutant.
Why this could be useful:
It helps developers see immediately where tests have blind spots.
Twister could offer a “mutation mode” similar to existing test/coverage modes.
Reports could include a mutation score, much like coverage reports.
Questions to the community:
➡️ Would this be valuable as a new feature in Twister?
➡️ Has there already been any discussion or workaround in this direction?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I was thinking it could be really interesting if Twister supported mutation testing.
The basic idea:
Twister would take the C source files under test,
apply targeted mutations (e.g. change operators, tweak constants, invert conditions),
rebuild the project,
run the tests again and check if the test suite “kills” the mutant.
Why this could be useful:
It helps developers see immediately where tests have blind spots.
Twister could offer a “mutation mode” similar to existing test/coverage modes.
Reports could include a mutation score, much like coverage reports.
Questions to the community:
➡️ Would this be valuable as a new feature in Twister?
➡️ Has there already been any discussion or workaround in this direction?
Best regards 👋
Beta Was this translation helpful? Give feedback.
All reactions