{
  "status": "research",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-12",
  "slug": "bounded-crash-testing",
  "term": "Bounded crash testing",
  "aliases": [
    "bounded black-box crash testing",
    "B3 crash testing"
  ],
  "definition": "Bounded crash testing systematically explores recovery behavior within an explicitly limited set of workloads, initial states and crash points.",
  "note": "CrashMonkey and ACE implement this approach for file systems; exhaustive coverage within selected bounds is not a proof covering every possible crash.",
  "related": [
    "crash-consistency",
    "crash-test-oracle",
    "fsync"
  ],
  "citations": [
    {
      "id": "mohan",
      "title": "Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju and Vijay Chidambaram. Finding Crash-Consistency Bugs with Bounded Black-Box Crash Testing. OSDI 2018, pp. 33-50; sections 3-6.",
      "url": "https://www.usenix.org/system/files/osdi18-mohan.pdf",
      "accessed": "2026-10-12"
    },
    {
      "id": "ace-docs",
      "title": "CrashMonkey project. ACE documentation: sequence lengths count core operations and the input space is bounded.",
      "url": "https://github.com/utsaslab/crashmonkey/blob/master/docs/Ace.md",
      "accessed": "2026-10-12"
    },
    {
      "id": "hesela",
      "title": "Hesela. Crash-consistency tests: the oracle is part of the result.",
      "url": "https://hesela.com/analyses/crash-testing-oracles-and-bounds/",
      "accessed": "2026-10-12"
    }
  ]
}