pub struct VerifyBlockResult {
pub name: String,
pub passed: usize,
pub failed: usize,
pub skipped: usize,
pub total: usize,
pub declared_passed: usize,
pub declared_failed: usize,
pub hostile_passed: usize,
pub hostile_failed: usize,
pub skipped_by_when: usize,
pub skipped_after_base_fail: usize,
}Fields§
§name: String§passed: usize§failed: usize§skipped: usizeCombined skipped count (when-driven plus base-fail-driven).
Kept for back-compat with consumers that don’t care about the
distinction; the split lives in the two fields below.
total: usize§declared_passed: usizeCases that originated from the user’s declared given list (or
the verify cases-form values they wrote literally). Always
populated under --hostile; under a non-hostile run, equal to
passed/failed and hostile_* are zero.
declared_failed: usize§hostile_passed: usizeCases injected by aver verify --hostile boundary expansion.
hostile_failed > 0 && declared_failed == 0 is the canonical
“your law passed on the values you wrote but breaks on the
boundary” signal — encode the missing precondition as when,
or drop the law form to a verify cases-form example.
hostile_failed: usize§skipped_by_when: usizeCases skipped because the user’s when predicate evaluated
to false. Subset of skipped. When this equals skipped and
no hostile profiles ran, the law is vacuously-under-hostile.
skipped_after_base_fail: usizeCases skipped because the same case_expr already failed in
its un-effected base world. Aver doesn’t run the VM for these
— they would only re-confirm the same counter-example under
harder worlds. Subset of skipped.
Trait Implementations§
Source§impl Clone for VerifyBlockResult
impl Clone for VerifyBlockResult
Source§fn clone(&self) -> VerifyBlockResult
fn clone(&self) -> VerifyBlockResult
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more