{
  "context": "This criteria evaluates how well the engineer uses QUnit's test lifecycle event hooks (begin, testStart, log, testDone, done) to capture and report test execution information. The focus is on proper usage of QUnit's event API rather than general coding practices.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "begin hook usage",
      "description": "Uses QUnit.begin() or QUnit.on('begin', ...) to capture when the test suite starts and correctly extracts the total test count from the details object",
      "max_score": 20
    },
    {
      "name": "testStart hook usage",
      "description": "Uses QUnit.testStart() or QUnit.on('testStart', ...) to capture when individual tests begin and correctly extracts test name and module information from the details object",
      "max_score": 20
    },
    {
      "name": "testDone hook usage",
      "description": "Uses QUnit.testDone() or QUnit.on('testDone', ...) to capture test completion and correctly extracts test results including success/failure status, duration (runtime), and test identification information",
      "max_score": 20
    },
    {
      "name": "log hook usage",
      "description": "Uses QUnit.log() or QUnit.on('log', ...) to capture detailed assertion-level information including failure messages, expected/actual values, and source information when available",
      "max_score": 20
    },
    {
      "name": "done hook usage",
      "description": "Uses QUnit.done() or QUnit.on('done', ...) to capture suite completion and correctly extracts summary information including total test count, passed count, failed count, and total runtime",
      "max_score": 20
    }
  ]
}