The kernel will move from truck to solidcore (#1597). The tests that must catch regressions across that switch are the ones that don't depend on the kernel: the reference tests and the robustness goldens. cargo-mutants checks whether they would notice a change in the kernel's behaviour. - apps/solidcraft-cli/tests/oracle_cases.rs: the reference tests as a cargo test (ignored; CI keeps replaying them through cargo xtask oracle), run over one process per core. - .cargo/mutants.toml: mutants are judged by that test and the pull-request sample of the robustness goldens, not by the kernel's own unit tests. - A mutants profile (ci with incremental builds): about 15 s to rebuild after a kernel change instead of about 3 minutes. - docs/mutation-testing.md: how to run it, its cost, two cargo-mutants 27.1 problems and the pilot's results (15% of sampled kernel mutants caught). Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
15 lines
968 B
TOML
15 lines
968 B
TOML
# cargo-mutants (docs/mutation-testing.md). Mutants are judged by the black-box suites that will
|
|
# outlive the kernel backend: the reference tests (tests/oracle, through the oracle_cases test)
|
|
# and the pull-request sample of the robustness goldens (every 8th seed, as ci.yml). The
|
|
# kernel's own unit tests are left out on purpose: a mutant only they catch is a behaviour the
|
|
# backend-neutral suites would miss when the kernel is swapped.
|
|
profile = "mutants"
|
|
additional_cargo_test_args = [
|
|
"--test", "oracle_cases", "--lib", "--", "--include-ignored",
|
|
"oracle_suite",
|
|
"robustness_goldens::seed_00", "robustness_goldens::seed_08", "robustness_goldens::seed_16",
|
|
"robustness_goldens::seed_24", "robustness_goldens::seed_32", "robustness_goldens::seed_40",
|
|
"robustness_goldens::seed_48", "robustness_goldens::seed_56", "robustness_goldens::seed_64",
|
|
"robustness_goldens::seed_72", "robustness_goldens::seed_80", "robustness_goldens::seed_88",
|
|
]
|