🤖 QA + AI
How to fit Claude and other LLMs into a real QA process — no magic, no hype. The model doesn't replace the tester: it removes the busywork so you can spend your head on risks and scenarios that actually need it. Below: articles and handy cheatsheets.
Articles
-
How QA Should Work with Claude: a Workflow, Not a Toy
Claude saves hours of QA busywork — if you treat it like a junior teammate, not a search box. A breakdown of the workflow, the tasks it closes, and where not to trust it.
-
QA Prompts: Templates That Actually Save Time
The formula for a good prompt plus seven ready-made templates for everyday testing tasks — from generating test cases to log analysis and requirements review.
-
AI bots that play your game: game-QA automation in 2026
AI agents for game testing: how they differ from scripted automation, what they actually do (24/7 exploratory play, crashes, balance, video logs), the limits and risks, who's on the market (modl.ai, AltTester, GameDriver), when to use AI bots and when plain automation is enough. A pilot checklist.
-
Claude in QA is overrated — 10 scenarios where it falls short, and where it actually pays off
The QA community has hyped «Claude will replace manual QA». In production those promises don't hold up. A contrarian breakdown without anti-AI rhetoric: 10 overrated scenarios, 5 systemic limits, hidden risks, and 5 places where it actually works.
-
AI and auto-healing locators in autotests — what actually works in 2026
The most expensive part of a mature autotest suite is locator maintenance. A whole class of products was built around that pain under the «AI-powered» label. 8 sections: what's under the hood, Healenium vs Mabl/testRigor/Functionize, where LLMs actually work, risks, and a rollout plan.
-
Claude for QA engineers: 10 real scenarios and prompts
AI assistants have moved from 'novelty' to legitimate working tool. For QA, this is especially powerful — routine tasks like test-case generation, log triage, prompt-shaped data.
Cheatsheet: the prompt formula
"You're a senior mobile QA" → "banking app, card-payment form, RU region" → "give negative cases" → "table: steps / result" → "poor network only, no duplicates".
What Claude closes — and what it doesn't
✅ Closes well
- Test cases and checklists from requirements or a screenshot
- Log and stacktrace analysis — find and group errors
- Test-plan and requirements review — gaps and contradictions
- Draft bug reports from raw notes
- Test data: boundary, invalid, edge cases
- Automation skeletons and manual-to-code conversion
- Routine writing: release notes, emails, translations
⚠️ Don't trust
- Your system's real behavior — it guesses
- Fresh versions, limits, APIs — verify them
- Counts and math without data
- The final call on quality — that stays with you
- Secrets, tokens, user PII — never paste them
Cheatsheet: quick templates
You're a senior QA. Feature: [description]. Constraints: [platform, region, limits]. Generate test cases grouped by: positive / negative / boundary / security / network. Format — a table: # / steps / expected result. No duplicates. Here's a log [paste]. Find the root error, group the repeats, explain unfamiliar exceptions in plain words, and suggest what to check first. Read these requirements [paste]. Find contradictions, ambiguity, invalid assumptions, missing scenarios (errors, offline, permissions). Ask questions where unclear. Turn notes into a bug report: [notes]. Format: title / steps / actual / expected / environment / severity. Flag what is missing. Give test data for the field [type: date / money / name]: valid, boundary, invalid, attacks (injections, unicode, emoji), local formats for [region]. Convert a manual case into a Playwright test with Page Object: [case]. Selectors by data-testid, explicit waits, no hardcoded delays. Point out where it is fragile. Three techniques that raise quality
- "Ask me 3 questions" before answering — accuracy jumps.
- Iterate, don't restart — critique the answer instead of starting over.
- Pin the format — "table only, no intro".
More deep-dives and practice on the Telegram channel.