{
  "context": "This criteria evaluates how well an engineer uses Ginkgo v2's basic test execution capabilities, specifically RunSpecs for suite integration and the framework's support for parallel execution. The focus is on proper usage of Ginkgo's core API elements for test suite setup and execution.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "RunSpecs usage",
      "description": "Uses RunSpecs function in a TestXxx function to integrate with Go's testing framework and execute the test suite. Should pass *testing.T to RunSpecs.",
      "max_score": 25
    },
    {
      "name": "Suite registration",
      "description": "Uses RegisterFailHandler to register Gomega's fail handler (Fail function) before calling RunSpecs, enabling proper assertion failures.",
      "max_score": 15
    },
    {
      "name": "Test organization",
      "description": "Uses Describe and/or Context container nodes to organize test specs into logical hierarchies (e.g., grouping by operation type).",
      "max_score": 20
    },
    {
      "name": "Spec definition",
      "description": "Uses It nodes to define individual test cases with clear, descriptive names that express the expected behavior.",
      "max_score": 15
    },
    {
      "name": "Gomega assertions",
      "description": "Uses Gomega matchers (e.g., Expect, To, Equal, HaveOccurred) within It blocks to verify expected behavior.",
      "max_score": 15
    },
    {
      "name": "Parallel compatibility",
      "description": "The test suite structure is compatible with parallel execution (can run with ginkgo -p) without requiring any Serial decorators or other parallel-specific workarounds for the simple test cases provided.",
      "max_score": 10
    }
  ]
}