Add mutant excludes for serde expecting messages
What the developer wrote
Authored by Jamil Lambert, PhD
Add mutant excludes for serde expecting messages
Two mutants were generated by replacing the `expecting` method of
serde visitors with a an empty string.
Add an exclusion for their `serde_details::Visitor` impl.
What changed, and why it matters
This commit only updates the project's mutation-testing configuration file. It tells the mutation-testing tool not to try altering certain serde visitor error-message methods, because those changes would not be meaningful to test. There is no code behavior change, no bug fix, and no security relevance.
No action needed; this is a benign configuration-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds one line to .cargo/mutants.toml under exclude_re, excluding serde_details::<impl de::Visitor<’_> from cargo-mutants mutation testing. This is a tooling-only change to avoid mutating serde’s expecting method into an empty string, which would only produce unhelpful test failures. No Rust source code is modified.
Changed components
.cargo/mutants.tomlInspect captured patch +1 / −0
diff --git a/.cargo/mutants.toml b/.cargo/mutants.toml
index 52de7abf..5334b2e1 100644
--- a/.cargo/mutants.toml
+++ b/.cargo/mutants.toml
@@ -9,6 +9,7 @@ exclude_re = [
"impl fmt::Debug",
".*Error",
"deserialize", # Skip serde mutation tests
+ "serde_details::<impl de::Visitor<'_>", # Skip serde mutation tests
"Iterator", # Mutating operations in an iterator can result in an infinite loop
# ----------------------------------Crate-specific exclusions----------------------------------
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.