Search / filter by team

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 — header search filters bracket by team and persists in URL",
  "description": "A search input in the header takes a team name (e.g. 'BRA' or 'Brazil') and narrows the bracket to fixtures involving that team. The current filter is encoded as ?team= in the URL so the filtered view is shareable.",
  "priority": "p2",
  "metadata": {
    "category": "surfaces",
    "stage": "all"
  },
  "planSteps": [
    {
      "type": "action",
      "description": "Navigate to the homepage"
    },
    {
      "type": "assertion",
      "description": "Verify a search input (visible <input type='search'> or <input> labeled 'team' / 'search') is present in the header / nav area"
    },
    {
      "type": "action",
      "description": "Type 'BRA' into the search input and submit or wait for filtering"
    },
    {
      "type": "assertion",
      "description": "Verify only fixtures involving Brazil are now visible in the bracket section (other fixtures hidden or visually de-emphasized)"
    },
    {
      "type": "assertion",
      "description": "Verify the URL now contains '?team=BRA' (or equivalent query parameter encoding) so the filter is shareable"
    }
  ]
}