{
  "context": "This evaluation assesses how well the engineer uses Ginkgo v2's execution tracing capability to generate trace files for performance analysis. The focus is on proper configuration and usage of the --execution-trace flag or equivalent programmatic approach.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "RunSpecs Configuration",
      "description": "Uses ginkgo.RunSpecs() to properly initialize the test suite with a testing.T instance and appropriate suite name",
      "max_score": 20
    },
    {
      "name": "Execution Trace Flag",
      "description": "Correctly configures execution trace generation using SuiteConfig with TraceWriter or uses the --execution-trace CLI flag to generate trace output to 'execution-trace.out'",
      "max_score": 40
    },
    {
      "name": "Test Organization",
      "description": "Uses Describe/Context/It blocks to organize calculator tests in a BDD style with clear test descriptions",
      "max_score": 15
    },
    {
      "name": "Gomega Assertions",
      "description": "Uses Gomega matchers (e.g., Expect().To(Equal())) for test assertions rather than standard Go testing assertions",
      "max_score": 15
    },
    {
      "name": "Trace File Generation",
      "description": "Successfully generates a trace file that can be verified to exist and is non-empty after test execution",
      "max_score": 10
    }
  ]
}