{
  "context": "This criteria evaluates how effectively the engineer uses the Ginkgo v2 testing framework to implement a suite bootstrapper. The focus is on proper usage of Ginkgo's suite initialization APIs, correct test file structure, and integration with Go's testing package as required by the Ginkgo framework.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "RunSpecs usage",
      "description": "Uses ginkgo.RunSpecs() function in the generated suite test function to integrate with Ginkgo's test runner. The function should be called with testing.T and a suite description string.",
      "max_score": 30
    },
    {
      "name": "Suite test function",
      "description": "Generates a test function with signature func TestXxx(t *testing.T) that serves as the entry point for the Ginkgo suite, following Go's testing conventions and Ginkgo's integration pattern.",
      "max_score": 20
    },
    {
      "name": "Suite file naming",
      "description": "Generates suite file with correct naming pattern: <package_name>_suite_test.go where package name is derived from the target directory or package.",
      "max_score": 15
    },
    {
      "name": "Package declaration handling",
      "description": "Correctly sets package declaration in generated suite file: uses package name with _test suffix for external testing (default) or without _test suffix when --internal flag is provided.",
      "max_score": 20
    },
    {
      "name": "Import statements",
      "description": "Includes necessary imports in generated suite file: 'testing' package and 'github.com/onsi/ginkgo/v2' package with appropriate import paths.",
      "max_score": 10
    },
    {
      "name": "Duplicate suite detection",
      "description": "Detects when a suite file already exists in the target directory and returns an appropriate error rather than overwriting or creating duplicate suite files.",
      "max_score": 5
    }
  ]
}