Match commentary excerpts

What TestSprite reads

The testing agent reads this JSON, opens the deployed URL in headless Chromium, executes each action step, evaluates each assertion. Verdict: passed / failed / blocked / inconclusive.

{
  "projectId": "1ad26753-ee03-4689-8f0f-6fa5d67c5c72",
  "type": "frontend",
  "name": "Surfaces — match detail page shows 2-3 sentence expert analysis specific to that fixture",
  "description": "Every /match/[id] page includes a commentary paragraph of at least 80 characters that reasons about THIS specific fixture (named teams, tactical points, recent form). Catches agents that ship a generic boilerplate paragraph reused across every match.",
  "priority": "p2",
  "metadata": {
    "category": "surfaces",
    "stage": "all"
  },
  "planSteps": [
    {
      "type": "action",
      "description": "Navigate to /match/r16-1"
    },
    {
      "type": "assertion",
      "description": "Verify a commentary / analysis paragraph of at least 80 characters is visible on the page (NOT the predicted score itself; NOT the team names alone)"
    },
    {
      "type": "assertion",
      "description": "Verify the commentary text mentions Brazil and Croatia by name (the two teams in this fixture)"
    },
    {
      "type": "action",
      "description": "Navigate to /match/r16-3 (a different fixture — France vs Germany)"
    },
    {
      "type": "assertion",
      "description": "Verify the commentary on /match/r16-3 mentions France and Germany — i.e. the commentary is fixture-specific, NOT a copy-pasted boilerplate from the previous page"
    }
  ]
}