{
  "context": "This criteria evaluates how well the engineer uses allure-python-commons lifecycle management API to implement a test result tracker. The focus is on correct usage of AllureLifecycle class methods for scheduling tests, managing steps, handling fixtures, and writing results.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "AllureLifecycle instantiation",
      "description": "Correctly imports and instantiates the AllureLifecycle class from allure_commons.lifecycle module in the __init__ method",
      "max_score": 10
    },
    {
      "name": "Test scheduling",
      "description": "Uses schedule_test_case() method to create and register new test cases in the create_test method, properly setting the test name and managing the test UUID",
      "max_score": 20
    },
    {
      "name": "Step lifecycle",
      "description": "Correctly uses start_step() and stop_step() methods to manage test steps in the add_step method, including proper parent_uuid handling for nested steps",
      "max_score": 25
    },
    {
      "name": "Before fixture",
      "description": "Uses start_before_fixture() and stop_before_fixture() methods to manage setup fixtures in the add_before_fixture method with correct parent_uuid association",
      "max_score": 15
    },
    {
      "name": "After fixture",
      "description": "Uses start_after_fixture() and stop_after_fixture() methods to manage teardown fixtures in the add_after_fixture method with correct parent_uuid association",
      "max_score": 15
    },
    {
      "name": "Status updates",
      "description": "Uses update_test_case() method or directly modifies test result status property to set test status (using Status enum from allure_commons.types or allure_commons.model2)",
      "max_score": 10
    },
    {
      "name": "Result finalization",
      "description": "Calls write_test_case() method to finalize and write the test result in the write_result method",
      "max_score": 5
    }
  ]
}