{
  "context": "This evaluation assesses how well an engineer uses the jest-expect-message package to build a performance benchmarking utility, focusing on proper usage of the library's optional message parameter and understanding of when performance overhead is applied.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Library setup",
      "description": "Correctly imports and configures jest-expect-message in the benchmark implementation, either via setupFilesAfterEnv or direct import",
      "max_score": 15
    },
    {
      "name": "Baseline assertions",
      "description": "Implements baseline scenario using expect() calls without the custom message parameter (2-parameter form), demonstrating understanding that this avoids overhead",
      "max_score": 25
    },
    {
      "name": "Enhanced assertions",
      "description": "Implements enhanced scenario using expect() calls with the custom message parameter (3-parameter form like expect(actual, 'message').toBe(expected)), demonstrating correct usage of the library's message feature",
      "max_score": 25
    },
    {
      "name": "Matcher compatibility",
      "description": "Uses standard Jest matchers (e.g., toBe, toEqual, toBeTruthy) correctly with both baseline and enhanced expect calls",
      "max_score": 15
    },
    {
      "name": "Timing measurements",
      "description": "Implements accurate performance measurements for both scenarios and calculates overhead percentage correctly",
      "max_score": 10
    },
    {
      "name": "Return structure",
      "description": "Returns object with required properties (baselineTime, enhancedTime, overheadPercent) with correct values",
      "max_score": 10
    }
  ]
}