Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for qa managers

Browser Support Matrix Update Agent

A support list that matches real usage and the code, verified by smoke tests on the minimum versions

DecisionsAnalysisIT and developmentProduct development
See how it worksGet access
Browser Support Matrix Update Agent: what goes in, what the agent does and what you get

What it does

The support list written two years ago no longer matches who visits the site. Each quarter this agent reads analytics for browser and version share, and compares it with the current support policy. It then checks which CSS and scripts the code actually uses against compatibility data, so it knows which features need which minimum version. It proposes an updated support list, for example dropping a version with 0.3 percent of traffic and adding a newer one. Before the lead reviews it, the agent runs a smoke test of the key pages on the proposed minimum versions and records any failures. If a minimum version fails, it adjusts the proposal and tests again. The lead approves the new policy. Edge case: a small browser share that produces most of the revenue is shown, not dropped.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueYes, continueApprovedNoNo 1 STARTS WHEN Quarterly review begins 2 USES A TOOL Read browser and version share from analytics 3 USES A TOOL Check used CSS and script features againstcompatibility data 4 DOES Propose an updated support list with the reasons 5 DOES Check revenue and conversion by browser for smallshares 6 USES A TOOL Smoke test key pages on the proposed minimumversions 7 CHECKS THE RESULT Do the key pages work on every minimum version? If not: raise that minimum or list the fix needed andupdate the proposal. Back to step 3. 8 DOES List features that need a fallback or polyfill 9 CHECKS THE RESULT Does the proposal cover at least 98 percent oftraffic? If not: lower the minimum for the largest uncoveredbrowser and retest. Back to step 3. 10 YOU APPROVE Lead approves the new policy 11 RESULT Updated support matrix and test list
Read the steps as a list
  1. Quarterly review begins
  2. Read browser and version share from analytics
  3. Check used CSS and script features against compatibility data
  4. Propose an updated support list with the reasons
  5. Check revenue and conversion by browser for small shares
  6. Smoke test key pages on the proposed minimum versions
  7. Do the key pages work on every minimum version?If not: raise that minimum or list the fix needed and update the proposal. Back to step 3.
  8. List features that need a fallback or polyfill
  9. Does the proposal cover at least 98 percent of traffic?If not: lower the minimum for the largest uncovered browser and retest. Back to step 3.
  10. Lead approves the new policyThe agent waits here for your OK.
  11. Updated support matrix and test list

How it decides

A version is supported if it has at least 1 percent of traffic or notable revenue, and the code works on it in a smoke test.

  • Support versions above 1 percent of traffic
  • Keep a browser with under 1 percent if it drives over 5 percent of revenue
  • Require a smoke test pass on each minimum version
  • Aim to cover 98 percent of traffic

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Traffic share threshold (default 1 percent)
  • Revenue share exception (default 5 percent)
  • Coverage target (default 98 percent)
  • Key pages to smoke test

What keeps you in control

It always asks you first

  • Publishing the new support policy

Hard limits

  • Never changes the live site or policy
  • Never drops a browser tied to meaningful revenue without showing it

It stops when

  • Done: proposal passes smoke tests and coverage target
  • Stop: analytics data is missing for the quarter

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensThe review found an old mobile browser at 0.4 percent of visits and 6 percent of revenue, so it stayed. Version 14 of another browser, at 0.2 percent, was proposed for removal. A smoke test on the proposed minimum for one browser failed on a CSS grid feature in the checkout page. The agent raised that minimum one version, retested to a pass, and coverage reached 98.6 percent.

More agents for qa managers

Quality control · Coding

Public Form Accessibility Agent

Every public form remains accessible after each revision.

7 steps2 checks5 jobs
Coding · Automation

Flaky Test Reproduction Agent

Every flaky test ends with a reproducible cause or a documented set of ruled-out causes.

9 steps1 check3 jobs
Coding · IT and development

Accessibility Regression Repair Agent

Keyboard and screen-reader journeys keep working after UI changes.

7 steps2 checks6 jobs
Coding · IT and development

Test Fixture Data Minimization Agent

Fixtures with no unnecessary personal data and all tests passing.

7 steps1 check2 jobs