{
  "context": "This criteria evaluates how effectively the engineer uses Jest's CLI filtering capabilities (--onlyFailures and --onlyChanged) to build a test result filter tool. The focus is on proper integration with Jest's programmatic API and CLI options for selective test execution.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Jest CLI Integration",
      "description": "Uses Jest's programmatic API or CLI to execute tests (e.g., via jest.runCLI(), spawning jest command, or @jest/core)",
      "max_score": 20
    },
    {
      "name": "Failure Filtering Implementation",
      "description": "Implements failure-based filtering using Jest's --onlyFailures (-f) option or equivalent programmatic approach to run only previously failed tests",
      "max_score": 25
    },
    {
      "name": "Change-Based Filtering Implementation",
      "description": "Implements change-based filtering using Jest's --onlyChanged (-o) option or equivalent programmatic approach to run tests for modified files",
      "max_score": 25
    },
    {
      "name": "Test History Tracking",
      "description": "Correctly captures and persists test results from Jest's output (e.g., test file paths and pass/fail status) to enable future filtered runs",
      "max_score": 15
    },
    {
      "name": "Configuration Pass-Through",
      "description": "Properly passes command-line flags to Jest (--failures-only maps to -f, --changed-only maps to -o) to activate the appropriate filtering mode",
      "max_score": 10
    },
    {
      "name": "Test Result Parsing",
      "description": "Correctly parses Jest's test results to extract relevant information (test paths, statuses) for history tracking, using Jest's output formats or result objects",
      "max_score": 5
    }
  ]
}