{
  "jira_key": "AN-39",
  "passed": true,
  "test_matrix": [
    {
      "name": "Auto-assign Customer Tier on Account creation",
      "type": "positive",
      "description": "When a new Account is created with a specific Annual Revenue, the Customer Tier field is automatically set according to the revenue-to-tier mapping.",
      "acceptance_criterion": "When an Account is created or its Annual Revenue changes, the Customer Tier field is automatically set according to the provided revenue-to-tier mapping."
    },
    {
      "name": "Auto-update Customer Tier on Annual Revenue change",
      "type": "positive",
      "description": "When an existing Account's Annual Revenue is updated, the Customer Tier field is automatically updated to reflect the new tier.",
      "acceptance_criterion": "When an Account is created or its Annual Revenue changes, the Customer Tier field is automatically set according to the provided revenue-to-tier mapping."
    },
    {
      "name": "Customer Tier not set if Annual Revenue is blank",
      "type": "negative",
      "description": "If an Account is created or updated with a blank Annual Revenue, the Customer Tier field should remain blank or set to a default value (as per business rules).",
      "acceptance_criterion": "When an Account is created or its Annual Revenue changes, the Customer Tier field is automatically set according to the provided revenue-to-tier mapping."
    },
    {
      "name": "Prevent manual edit of Customer Tier via UI",
      "type": "positive",
      "description": "Users cannot manually edit the Customer Tier field on the Account Lightning Record Page.",
      "acceptance_criterion": "Users cannot manually edit the Customer Tier field."
    },
    {
      "name": "Attempt to edit Customer Tier via API or Data Loader is blocked",
      "type": "negative",
      "description": "If a user attempts to update the Customer Tier field directly via API or Data Loader, the update is blocked by the validation rule.",
      "acceptance_criterion": "Users cannot manually edit the Customer Tier field."
    },
    {
      "name": "Customer Tier field is visible on Account Lightning Record Page",
      "type": "positive",
      "description": "The Customer Tier field is displayed on the Account Lightning Record Page for users with the appropriate permission set.",
      "acceptance_criterion": "The Customer Tier field is visible on the Account Lightning Record Page."
    },
    {
      "name": "Customer Tier field not visible without permission set",
      "type": "negative",
      "description": "A user without the Account_Customer_Tier_Visibility permission set does not see the Customer Tier field on the Account Lightning Record Page.",
      "acceptance_criterion": "The Customer Tier field is visible on the Account Lightning Record Page."
    },
    {
      "name": "Backfill Customer Tier for existing Accounts",
      "type": "manual",
      "description": "Run the backfill process to update all existing Accounts with the correct Customer Tier based on their current Annual Revenue.",
      "acceptance_criterion": "Existing Accounts can be backfilled with the correct Customer Tier based on current Annual Revenue."
    },
    {
      "name": "Backfill does not overwrite manually set Customer Tier (if any pre-existing)",
      "type": "manual",
      "description": "Verify that the backfill process does not overwrite Customer Tier values that were previously set manually (if applicable to legacy data).",
      "acceptance_criterion": "Existing Accounts can be backfilled with the correct Customer Tier based on current Annual Revenue."
    }
  ],
  "apex_tests_run": 0,
  "apex_tests_passed": 0,
  "apex_failures": [],
  "manual_scenarios": [
    "Backfill Customer Tier for existing Accounts",
    "Backfill does not overwrite manually set Customer Tier (if any pre-existing)"
  ],
  "summary": "QA passed \u2014 acceptance criteria covered; no Apex classes in this change",
  "notes": null
}