{
  "context": "This evaluation assesses how well the engineer implements test tracking mechanisms following karma-qunit's dual-strategy pattern. It focuses on whether they correctly implement native test count detection, fallback manual counting, and proper test lifecycle tracking as used in karma-qunit adapters.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Dual tracking strategy",
      "description": "Implements both native tracking (checking for totalTests property) and fallback manual counting, mirroring karma-qunit's approach of using QUnit.totalTests when available and manual counting otherwise",
      "max_score": 25
    },
    {
      "name": "Native count detection",
      "description": "Correctly checks for and uses the totalTests property from the test framework in the onBegin handler, similar to karma-qunit's detection of QUnit.config.totalTests or QUnit.totalTests",
      "max_score": 15
    },
    {
      "name": "Manual counter initialization",
      "description": "Initializes a manual test counter (starting at 0) when native totalTests is unavailable, following karma-qunit's fallback counting strategy",
      "max_score": 15
    },
    {
      "name": "Test start counting",
      "description": "Increments the manual counter when onTestStart is called and native tracking is unavailable, matching karma-qunit's testStart event handler behavior",
      "max_score": 15
    },
    {
      "name": "Statistics reporting",
      "description": "Implements getStats method that returns the total test count (either from native totalTests or manual counter) along with test execution statistics, similar to karma-qunit's tc.info() reporting",
      "max_score": 15
    },
    {
      "name": "Test lifecycle tracking",
      "description": "Correctly tracks test started count, completed count, and pass/fail status across onTestStart and onTestDone handlers, following karma-qunit's lifecycle event pattern",
      "max_score": 15
    }
  ]
}