1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
//! Auto-generated mutation-killing **system tests** for `crates/mega-evm/src/`.
//!
//! # What lives here
//!
//! This directory holds tests that were generated by the mutation-improvement
//! workflow (the `improve-mutation-score` skill) to close *specific* surviving
//! mutants surfaced by `cargo-mutants`. Each submodule targets the survivors of
//! one source area; every test maps back to a concrete mutant and kills it by
//! either asserting an exact value (constants, discriminants, computed limits)
//! or observing a behavioral difference through the public EVM harness.
//!
//! # Scope: system tests only
//!
//! Only **system / integration-level** tests belong here — those that exercise
//! mega-evm through its public (or `test-utils`-gated) API end-to-end, because
//! the mutant they kill is only observable through whole-EVM behavior.
//!
//! A mutant that can be killed by a **unit test** of one module does **not**
//! belong here: put that test inline next to the code it covers, in the source
//! module's own `#[cfg(test)] mod tests`. Reserve this directory for the cases
//! that genuinely need a full-execution harness to observe.
//!
//! Mutants found to be provably equivalent or dead are not tested at all — they
//! are recorded in `mutants/suppressions.toml` with a justification and reviewer.
//!
//! # Do not hand-edit
//!
//! These tests are **machine-generated and machine-maintained**. Treat them as
//! generated artifacts:
//!
//! - Do **not** rename, reword, or refactor them by hand — each test is keyed to a mutant, and
//! editing it can silently stop it from killing that mutant.
//! - Do **not** add unrelated assertions here; write ordinary tests in the relevant module or the
//! spec-organized suites under `tests/` instead.
//! - To close a *new* survivor, re-run the `improve-mutation-score` skill rather than authoring a
//! test here manually, so it stays linked to its mutant and the suppression bookkeeping stays
//! consistent.
//!
//! If a test here is wrong or stale, fix the source/suppression and regenerate;
//! don't patch the generated test in place.
//!
//! See `mutants/README.md` and the `improve-mutation-score` skill for the full
//! methodology.