{
  "context": "This criteria evaluates how well the engineer uses the Ginkgo CLI tool's build configuration capabilities to create a test runner. The focus is on proper usage of the ginkgo command with flags like --race, --cover, --tags, and --ldflags to control test compilation and execution.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses ginkgo CLI",
      "description": "Invokes the 'ginkgo' command (or ginkgo.GetSuite() programmatically) rather than implementing test execution from scratch or using 'go test' directly",
      "max_score": 25
    },
    {
      "name": "Race detection flag",
      "description": "Correctly passes the --race flag to the ginkgo command to enable the race detector during test execution",
      "max_score": 15
    },
    {
      "name": "Coverage flag",
      "description": "Correctly passes the --cover flag (or --coverprofile) to enable code coverage and generate coverage profiles",
      "max_score": 15
    },
    {
      "name": "Build tags support",
      "description": "Correctly passes the --tags flag to the ginkgo command to support conditional compilation with custom build tags",
      "max_score": 20
    },
    {
      "name": "Linker flags support",
      "description": "Correctly passes the --ldflags flag to the ginkgo command to pass custom flags to the linker during compilation",
      "max_score": 15
    },
    {
      "name": "Flag composition",
      "description": "Properly handles multiple flags together in a single command execution, allowing users to combine --race, --cover, --tags, and --ldflags",
      "max_score": 10
    }
  ]
}