public record class FuzzOutcomeWhat a run came to.
No guide page documents this yet — the page shows what the code says about itself.
Fields and properties (9)
public string TargetWhich decoder was run.
public long CasesHow many inputs were pushed through it.
public int CorpusSizeHow many were worth keeping.
public int SignaturesHow many distinct behaviours were seen.
public TimeSpan ElapsedHow long it took.
public IReadOnlyList<FuzzFinding> FindingsWhat broke, if anything.
public string StoppedWhy the run ended, as a phrase for the summary line. ⚠ Not decoration. A run that stopped on the finding cap and a run that used its whole budget print the same line without this, and the two mean opposite things: raven's nightly saturated MaxFindings after five and a half minutes of a two-hour budget for weeks, and the summary said 3 FINDING(S) in exactly the tone it would have said it after two hours. What caught it was somebody downloading an artifact and counting the files in it.
public long SuppressedHow many further failures matched a finding already held. The other half of the same signal. One defect reached ten thousand ways is a number worth printing, both because it says the finding list is short for a good reason and because a suppressed count that dwarfs the run is a key that is still splitting one bug into many.
public bool CleanWhether every promise held.
Methods (2)
public FuzzOutcome(string Target, long Cases, int CorpusSize, int Signatures, TimeSpan Elapsed, IReadOnlyList<FuzzFinding> Findings, string Stopped, long Suppressed)What a run came to.
public override string ToString()Returns a string that represents the current object.
Used by (4)
- CaseGuardTestsVixen.Fuzz.Tests
- FindingDedupTestsVixen.Fuzz.Tests
- FuzzGateTestsVixen.Fuzz.Tests
- FuzzSessionVixen.Fuzz