Example · Test Analyst (manual / UAT)

58% of your week as a test analyst is still yours.

AI now drafts test cases and runs scripts. Getting the business to test and signing the result stays with you.

Make my planA typical week at the middle pace. Your plan uses your own tasks.

Is manual testing a dying career?

In a typical week at the middle pace, 38% of this work needs your judgment and 20% is work you do using AI. AI could do about 42%. Drafting and running cases is what models already do well, and it is 42% of your week. It is also what you were hired to do.

Read more

That work covers cases from a story, the scripted run, the defect write-up and the Friday status report. If you have tried a drafting tool on a story, you have seen it produce thirty cases in a minute. After an hour of tidying, a day of your work is done.

The same trial shows what holds. A few of those cases usually test a rule that no longer exists, and nobody but a person who knows the product notices. The job now has four parts. You know whether a case proves anything, you tell a defect from a business rule working as designed, you get a business user to sit down and look, and you put your name on the report that says the release was tested. Most test analysts already do all four, informally. The title says you write and run cases. Two tasks people often dislike are the completion report and the environment chase. This report helps you take ownership of both. Before the AI part, note that the biggest risk to this seat is older than any model. Manual testing has been moved offshore for twenty years, and many test teams are already half vendor. We score that separately, and it comes first.

The week, task by task

Who does each hour of a typical 40-hour week.

See every task
You38% · 15 hours

Needs your judgment.

  • Chasing environments, access, data refreshes and release windows9%
  • Running UAT with business users: scheduling, sitting with them, interpreting what they found8%
  • Regression scoping: which existing cases to re-run for this change6%
  • Test planning and the risk-based approach for a release6%
  • + 2 smaller tasks9%
You using AI20% · 8 hours

AI does the slow parts. You still own it.

  • Requirements review: finding gaps and ambiguities before build7%
  • Defect triage with developers and BAs: defect, requirement gap, or working as designed7%
  • Test data: choosing and setting up the records and edge cases6%
AI42% · 17 hours

AI could do most of it.

  • Writing test cases from stories and requirements (Xray, ALM or similar)16%
  • Raising defects: steps, screenshots, proposed severity8%
  • Executing scripted manual runs and recording pass/fail8%
  • Status reports, traceability matrix upkeep, dashboards6%
  • + 1 smaller task4%
Why some tasks still need a person
"Is this a defect, or is that how the rating engine works?"

This takes context. The answer lives in the product rules, the odd cases a particular record carries, and years of watching what the program broke. A model can read the requirement, but it cannot know that the requirement was wrong and everyone agreed to leave it.

Knowing which records to test with

This takes context, and errors are costly to catch. A wrong premium or payment looks exactly like a right one until a letter goes out. Your test data encodes which records have the odd endorsements and mid-term changes. Nobody wrote that list down.

Getting the business users into the UAT room

This takes presence and trust. Business users test when someone they trust asks them, walks them through it and writes down what they say. A model can send the invite, but it cannot be the reason a claims handler gives up a Thursday afternoon.

Signing the test completion report

You carry this accountability for the employer. The report is the evidence that a release was tested before go-live, and internal audit tests that control. Someone named has to sign. Often, informally, that is the test analyst, beneath the test lead.

Spotting the generated cases that test a rule you removed

This is checking work. A tidy case that proves nothing is the costliest kind of error, because it passes. The person who can read thirty cases and say "two of these are dead" is the constraint on every case-generation tool.

Good to know

What is hard about this field, and what you can do about it.

The hard truth

Many testers now automate as well as design tests.

In a 2023 developer survey, most people involved in testing said they write automated tests. A role that only runs scripts by hand is the narrowest version of this job, and the hardest to defend.

What you can doScript-writing is where AI tools landed first, so put your effort where judgment counts: acceptance, test data and the review of generated cases. Show the defects you caught and the hours you saved.
Sources (2)

What's next for a manual tester?

Plan A is the best move inside the work you do now.

APlan A

Grow in the job you have

The main focus. Most weekly sessions build toward it.

Your next stepBecome the named UAT coordinator and acceptance author
Each week
4 sessions
Ready in
About 5 weeks for a first acceptance statement
Why it fits

Why you. You already get the business users into the room and you already draft the report someone else signs. Business users return your calls, and nobody on the vendor side has that standing. The gap between what you do and what your title says is smaller here than for your other moves.

The gap. Usually no written acceptance statement exists. The completion report is a template with a traffic light. No business owner signs beside the test team. The UAT schedule lives in a shared mailbox.

The trade-off. Your name is on record when a release goes wrong. The pressure stays the same, but you gain authority. You will write fewer cases for a quarter, and your test lead has a cases-per-analyst number somewhere. The seat is also tied to programs. It moves with you to the next program, but not to a business-as-usual (BAU) support team.

2 other moves that fit
  • Own the quality of machine-written test casesReady in about 4 months
  • Back-up plan: domain tester, with a path to business analystReady in about 10 weeks

What's a plan B for test analysts and UAT testers?

Plan B is meant to be different from this job. It was picked because skills from this role carry over.

BPlan B

Get ready for a new kind of job

A second option. A newer job AI is creating that these skills already fit.

A job to aim forAgent simulation scenario designer

Turning real user steps into clear UAT scripts is what agent simulation needs, with customer conversations as the test cases.

Each week
1 session
Outlook
Next wave
Pay
$25 to $45 an hour (contract)One OpenTrain AI agent evaluation contract listing, 2026.
2 other options
  • AI evaluation specialistSigning off on whether the business can accept a release is the same call evaluators make about AI outputs, case by case.
  • Expert AI trainer (contract)Grading outputs against expected results is how platforms test trainers, and your domain knowledge sets your pay tier as bridge income.

In your own plan you can switch to any of the 47 roles.

The 13 weeks

Small steps that add up. One plan for both: most sessions build Plan A, one a week builds Plan B.

By week 13 you will have

AFor Plan A

  • Two one-page acceptance statements for real releases
  • A review checklist for AI-written test cases
  • A memo asking to be named UAT coordinator

BAnd for Plan B

  • A scenario scoring guide
  • A published agent test suite for your portfolio
Month 1Weeks 1 to 4
  1. 1Measure your week
  2. 2Learn the tool and audit rules
  3. 3Study defects that slipped through
  4. 4Write a review checklist

You finish withA revised checklist and a count of disagreements

Month 2Weeks 5 to 8
  1. 5Write your first acceptance page
  2. 6Fix the test environment schedule
  3. 7Make UAT easy for users
  4. 8Trim the regression suite

You finish withA log of twenty retired or rewritten cases

Month 3Weeks 9 to 13
  1. 9Second acceptance page and ask
  2. 10Check the job market
  3. 11Gather your evidence
  4. 12Send the memo and ask
  5. 13Build your portfolio and apply

You finish withOne application sent with your portfolio

Three courses from the plan
  • ISTQB Certified Tester Foundation Level (CTFL) v4.0 (syllabus 4.0.1)ISTQB via ASTQB / AT*SQA (US exam) · $229

    Only if a posting you want asks for it. Many bank and insurer HR screens do. It teaches vocabulary more than judgment.

  • ISTQB Advanced Level Test Analyst (CTAL-TA) v4.0ISTQB via AT*SQA · $249

    It is the one ISTQB exam that describes your durable work. Even so, take it in months 4 to 6, only if postings ask, and only v4.0.

  • ISTQB Acceptance Testing (CT-AcT)ISTQB via AT*SQA · $199

    Read the free sample exam first. The syllabus predates every tool in this report. Buy only if you want the vocabulary for Plan A on a résumé.

Checked 2026-10-11.

The fuller picture

Risks beyond AI: highOffshore and program risk

Offshoring outranks AI here. Manual test execution has been offshored on cost since before today's tools existed, and enterprise test teams are often mostly vendor staff already. Many test analysts are also employed by a program. When the platform goes live, the test team shrinks, with or without an agent. We score this separately because blaming AI for it would get the remedy wrong.

Where this could be wrong
  • UAT facilitation may be more exposed than we scored. Our capability score assumes a business user needs a trusted person in the room. If your business users are comfortable with a guided walkthrough tool that records what they do, that task becomes more exposed, and the UAT coordinator move leans harder on the acceptance statement than on being in the room.
  • We assumed the completion report is yours informally. If a release manager already signs and you only prepare, the UAT coordinator move is "get your name on it," not "own it," and that task gives you less protection.
  • The offshore ratio may already be the ceiling. If your employer has a policy floor on onshore testers for data-handling reasons, the non-AI volatility is lower than "high" and the AI risk moves back to first place.
  • Environment chasing may be going away on its own. If the program moves to a cloud platform with self-service environments, a chunk of your lasting work disappears and the split of your week looks worse, though your position does not.

This is an example. Your plan uses your own week.

Make my plan

Also matched: test analyst, uat analyst, uat tester. Research checked 2026-10-11. Page updated .