{
  "context": "This evaluation assesses the engineer's ability to use pytest-redis's three-level configuration system (factory arguments, CLI options, pytest.ini) to create custom Redis fixtures with proper precedence handling.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Factory functions used",
      "description": "Uses pytest_redis.factories.redis_proc() and/or pytest_redis.factories.redisdb() to create custom Redis fixtures rather than relying solely on built-in fixtures.",
      "max_score": 25
    },
    {
      "name": "pytest.ini configuration",
      "description": "Creates or uses a pytest.ini (or pyproject.toml/tox.ini) file with pytest-redis configuration options (e.g., redis_port, redis_host) to demonstrate lowest-precedence configuration.",
      "max_score": 20
    },
    {
      "name": "Factory argument override",
      "description": "Passes configuration parameters directly to factory functions (e.g., port=6382, host='localhost') to demonstrate highest-precedence configuration that overrides CLI and ini settings.",
      "max_score": 25
    },
    {
      "name": "CLI option handling",
      "description": "Demonstrates understanding of CLI configuration by either using pytest command-line options (--redis-port, --redis-host) in test execution or by using pytest's request.config mechanism to simulate CLI configuration.",
      "max_score": 15
    },
    {
      "name": "Precedence verification",
      "description": "Tests correctly verify the three-level precedence hierarchy by asserting that the Redis connection uses the expected configuration from the appropriate level (checking port/host from connection info or server process).",
      "max_score": 15
    }
  ]
}