@MarcoFalke / @practicalswift I’m starting some mutation analysis using https://github.com/agroce/universalmutator
A couple of questions:
-
At random I picked
tx_verify.cpp
as a file with high coverage that is likely critical, where any missed non-equivalent mutants should be carefully investigated. Is this a good choice to get the workflow going on? -
Is there any mapping from fuzz targets to code expected to be covered? I can run all targets, of course, but knowing which ones might possibly detect
tx_verify.cpp
mutants would be helpful.