This QA tester test is a free, 20-question software testing quiz you can take right here, with an instant score and an explanation for every answer. It's built for three kinds of people: job seekers checking they're ready before a QA interview, career switchers who want to know where they stand, and hiring managers who need a quick first screen for junior QA candidates.
No sign-up, no email, no timer. Answer the questions, see your score, and get a clear recommendation for what to study next.
What Is the QA Tester Test?
The QA tester test is a free online QA skills test with 20 multiple-choice questions at entry and junior level. It covers testing basics, test design, bug reporting, test types and Agile, and automation and APIs. You get an instant score out of 20, the correct answer and a one-line explanation for each question.
It works like a short QA tester assessment: the same kind of questions you'll meet in screening quizzes and first-round interviews, without the pressure. It takes about 10 to 15 minutes.
What the QA Tester Test Covers
The 20 QA test questions are split evenly across five topic areas, four questions each:
| Topic area | Questions | What it checks |
|---|---|---|
| Testing basics | 4 | QA vs QC, verification vs validation, test case vs test scenario, the testing life cycle |
| Test design | 4 | Boundary value analysis, equivalence partitioning, negative testing, test case fields |
| Bugs & reporting | 4 | Severity vs priority, writing a good bug report, the bug life cycle, intermittent bugs |
| Test types & Agile | 4 | Smoke vs regression testing, UAT, Scrum's Definition of Done, exploratory testing |
| Automation & APIs | 4 | What to automate first, flaky tests, HTTP status codes, Playwright locators |
The questions use standard terminology (ISTQB Foundation definitions where they matter) and avoid trick wording. Each one has exactly one correct answer.
Take the QA Tester Test
20 questions across 5 areas. Pick an answer to see whether it's right and why. Your score and a breakdown by topic appear at the end.
1/20 · Testing basics Which statement best describes the difference between quality assurance (QA) and quality control (QC)?
2/20 · Testing basics Validation answers which question?
3/20 · Testing basics What is the main difference between a test scenario and a test case?
4/20 · Testing basics In a typical software testing life cycle (STLC), which of these activities comes first?
5/20 · Test design An age field accepts whole numbers from 18 to 60 inclusive. Using boundary value analysis (each boundary plus the value just outside it), which set of values should you test?
6/20 · Test design A shop gives no discount for 1 to 9 items, 10% for 10 to 49 items, and 20% for 50 or more items. Using equivalence partitioning, what is the minimum number of test values needed to cover every valid partition once?
7/20 · Test design Which of these is a negative test for a login form?
8/20 · Test design Which test case field lets a tester decide whether the test passed or failed?
9/20 · Bugs & reporting The company name is misspelled in the logo on the home page, but every feature works. How is this bug usually classified?
10/20 · Bugs & reporting Which is the most useful bug report title?
11/20 · Bugs & reporting A developer marks your bug as Fixed. What should you normally do next?
12/20 · Bugs & reporting You saw the app crash once but cannot make it happen again. What is the best action?
13/20 · Test types & Agile What is the main difference between smoke testing and regression testing?
14/20 · Test types & Agile Who typically performs user acceptance testing (UAT)?
15/20 · Test types & Agile In Scrum, what is the "Definition of Done"?
16/20 · Test types & Agile Which best describes exploratory testing?
17/20 · Automation & APIs Which tests are usually the best candidates to automate first?
18/20 · Automation & APIs What is a flaky test?
19/20 · Automation & APIs A GET request to /api/users/999 returns HTTP status 404. What does that mean?
20/20 · Automation & APIs Playwright is an open-source browser automation framework. In Playwright, what is a locator?
Your level: Foundations
You're at the start of the QA path, and that's the right time to learn the fundamentals properly: test cases, bug reports, test types and how QA works in an Agile team.
Your level: Ready to grow
You know the basics. The next step is using AI tools in your testing, then moving into automation, which many QA job ads now ask for.
Your level: Automation-ready
Strong fundamentals. You're ready to learn test automation with Playwright and AI, and to prove it with exam-style practice questions.
Answer key: QA tester test questions and answers (open after you finish)
- Which statement best describes the difference between quality assurance (QA) and quality control (QC)?
Answer: B. QA focuses on the process to prevent defects; QC checks the product to find defects. QA is process-oriented and aims to prevent defects, while QC is product-oriented and aims to detect them (testing is a major part of QC). - Validation answers which question?
Answer: A. Are we building the right product, the one users actually need? Validation checks the product meets the users' real needs ("right product"); verification checks it meets the specified requirements ("product right"). - What is the main difference between a test scenario and a test case?
Answer: C. A test scenario is a high-level idea of what to test; a test case gives the exact steps, test data and expected result. "Verify a user can log in" is a scenario; a test case turns it into specific preconditions, steps, data and an expected result. - In a typical software testing life cycle (STLC), which of these activities comes first?
Answer: B. Requirement analysis. Testers first analyse the requirements to understand what is testable; execution, retesting and closure all come later. - An age field accepts whole numbers from 18 to 60 inclusive. Using boundary value analysis (each boundary plus the value just outside it), which set of values should you test?
Answer: D. 17, 18, 60 and 61. The boundaries are 18 and 60, and the nearest invalid values just outside them are 17 and 61. - A shop gives no discount for 1 to 9 items, 10% for 10 to 49 items, and 20% for 50 or more items. Using equivalence partitioning, what is the minimum number of test values needed to cover every valid partition once?
Answer: B. 3. There are three valid partitions (1-9, 10-49, 50+), so one representative value from each, such as 5, 20 and 75, covers them all. - Which of these is a negative test for a login form?
Answer: C. Enter a valid username with a wrong password and check that login is refused with a clear error. Negative testing feeds invalid or unexpected input and checks the system handles it gracefully instead of accepting it. - Which test case field lets a tester decide whether the test passed or failed?
Answer: A. Expected result. The tester compares the actual result with the expected result; without an expected result there is no objective pass/fail decision. - The company name is misspelled in the logo on the home page, but every feature works. How is this bug usually classified?
Answer: D. Low severity, high priority. It has little functional impact (low severity) but is visible to every visitor and hurts the brand, so it should be fixed quickly (high priority). - Which is the most useful bug report title?
Answer: C. Checkout: "Place order" button does nothing when the cart contains a discounted item. A good title says where the problem is, what happens and under which condition, so anyone can understand it without opening the report. - A developer marks your bug as Fixed. What should you normally do next?
Answer: A. Retest it on the new build, then close it if it is fixed or reopen it if it is not. In the bug life cycle a fixed bug is retested (confirmation testing) by QA before it is closed or reopened. - You saw the app crash once but cannot make it happen again. What is the best action?
Answer: B. Report it with everything you know (steps, time, environment, logs, screenshots) and note that it is intermittent. Intermittent bugs are still bugs; honest details and logs help developers find the cause, while claiming 100% reproducibility misleads them. - What is the main difference between smoke testing and regression testing?
Answer: A. Smoke testing quickly checks that a build's critical functions work; regression testing checks that changes have not broken existing functionality. A smoke test is a short, broad check that a build is stable enough to test further; regression testing re-checks existing features after a change. - Who typically performs user acceptance testing (UAT)?
Answer: D. End users, customers or business representatives. UAT checks the system meets business needs, so it is done by the people who will use or own the product. - In Scrum, what is the "Definition of Done"?
Answer: C. A shared set of quality criteria (for example code reviewed, tests passing) that work must meet before it counts as complete. The Definition of Done is the team's agreed quality bar; work that does not meet it is not considered done. - Which best describes exploratory testing?
Answer: B. Designing and running tests at the same time, using what you learn about the app to decide what to test next. Exploratory testing is structured learning: the tester designs and executes tests on the fly, often within a time-boxed charter, and records findings. - Which tests are usually the best candidates to automate first?
Answer: D. Stable, repetitive checks that run often, such as login and checkout regression tests. Automation pays off on stable tests that are run many times; one-off, changing or judgement-based checks are better done manually. - What is a flaky test?
Answer: A. A test that sometimes passes and sometimes fails without any change to the code or the test. Flaky tests give inconsistent results for the same code, often due to timing, shared test data or unstable environments, and they erode trust in the suite. - A GET request to /api/users/999 returns HTTP status 404. What does that mean?
Answer: C. The requested resource was not found. 404 means Not Found; 200 means OK, 201 means Created and 500 means Internal Server Error. - Playwright is an open-source browser automation framework. In Playwright, what is a locator?
Answer: D. A way to find elements on the page, such as page.getByRole('button', { name: 'Submit' }). A locator describes how to find element(s) on the page; Playwright looks it up when you act on it and auto-waits for the element to be ready.
What Your Score Means
Your score points you to the right next step. Be honest with yourself: a lucky guess today is a gap in an interview tomorrow.
0 to 9: Foundations
You're at the start, and that's fine. Learn the core vocabulary and techniques first: test cases, bug reports, test design and how testing fits into a team. Start with Manual Testing & QA with AI: ChatGPT, Claude AI 2026, which is built around landing a first QA job. If you'd rather go straight into AI-assisted testing without writing code, AI Software Testing for Beginners: QA Career with No Coding is the alternative starting point.
10 to 15: Ready to grow
You know the fundamentals, with a few gaps. Re-read the explanations for the questions you missed, then build on what you know. AI Software Testing for Beginners shows you how to use AI in everyday testing work, and once that feels comfortable, Playwright + Claude AI & MCP Server: AI QA Automation 2026 takes you into automation, teaching JavaScript as you go.
16 to 20: Automation-ready
Your fundamentals are solid. The skill that most often separates junior testers from automation roles is writing and maintaining automated tests. Playwright + Claude AI & MCP Server: AI QA Automation 2026 builds a full Playwright framework with you, and the Playwright Automation Practice Tests let you check that knowledge with exam-style questions.
How to Prepare for a QA Tester Interview
A good score on this software testing quiz is a start. Interviews go further: you'll be asked to explain your answers, write a test case on the spot, or talk through a bug you found. Here's how to prepare:
- Know the testing types by name and purpose. Interviewers expect you to tell smoke, sanity, regression, integration and UAT apart. The types of software testing guide covers 20+ types with examples.
- Practise writing test cases and bug reports. Many interviews include a practical task. Use the free test case and bug report templates to practise the format until it's second nature.
- Rehearse common interview questions out loud. Work through the 40 software testing automation interview questions and answer each one in your own words, with an example from a project.
- If the role mentions automation, prepare for Playwright. The Playwright interview questions for 2026 cover locators, waits, fixtures and CI.
- Take the next level test. Scored 16 or more here? Try the free Playwright quiz, 15 multiple-choice questions on Playwright itself.
New to the field? Read what QA testing is and what a QA tester does day to day before your first interview, so you can describe the job in your own words.
Using This Test to Screen QA Candidates
Hiring managers are welcome to use this QA skills test as a quick, free first filter for junior and entry-level QA roles. Send candidates the link and ask them to share their score.
Some honest caveats:
- It's a first filter, not a hiring decision. Twenty multiple-choice questions show whether someone knows core terms and techniques. They don't show how a person thinks, communicates or investigates a real bug.
- It isn't proctored. Candidates take it on their own, can retake it, and each answer is explained as soon as they pick it. Treat the score as a conversation starter, not proof.
- It targets entry level. It won't separate a mid-level tester from a senior one. For automation roles, follow up with a practical task.
- Follow up in the interview. Pick two or three questions and ask the candidate to explain the answer in their own words, or to give an example from their own work. That tells you far more than the number.
A practical exercise works well as the second step: give candidates a simple form or page and ask them to write three test cases and one bug report.
Frequently Asked Questions
Is the QA tester test free?
Yes. The test is completely free, with no sign-up and no email required. You get your score, the correct answers and an explanation for every question as soon as you finish.
How long does the QA tester test take?
The 20 questions take about 10 to 15 minutes. There is no timer, so you can take as long as you need.
Is this like the QA skills tests employers use, such as TestDome?
It covers similar ground at entry level: testing fundamentals, test design, bug reporting, Agile and basic automation. It's shorter, untimed and not proctored, so treat it as practice and a self-check rather than a certification.
What is a good score on the QA tester test?
16 or more out of 20 means your fundamentals are solid and you're ready to focus on automation. 10 to 15 means you know the basics with some gaps. Below 10 means it's worth studying the fundamentals before interviews.
Can employers use this test to screen QA candidates?
Yes, as a quick first filter for junior roles. It isn't proctored and can be retaken, so use the score to start a conversation, then follow up with interview questions and a short practical task before making any hiring decision.
What should I study after the QA tester test?
Review the explanations for any questions you missed, then follow the recommendation for your score band. For interview prep, practise writing test cases and bug reports, learn the main types of testing, and rehearse common QA interview questions out loud.
Asim Noaman
Senior QA Automation Engineer & AI Testing Specialist
With years of hands-on experience building test automation frameworks for production applications, Asim specializes in combining traditional QA methodologies with cutting-edge AI tools. He has helped teams adopt Playwright and AI-driven testing workflows to ship faster with fewer bugs.
Start Your QA Career
Turn Your Score Into Your First QA Job.
Whatever you scored, the fastest way to close the gaps is to learn the fundamentals in order and practise them on real examples. Manual Testing & QA with AI walks you through the skills this test checks, from test cases and bug reports to Agile teamwork, and shows you how to use ChatGPT and Claude AI to work faster.
- Test design, test cases and bug reports, step by step
- How testing works inside an Agile team
- Using ChatGPT and Claude AI in everyday QA work
- 4.5★ on Udemy, 660+ students, 30-day money-back guarantee
Prefer no-code AI testing? AI Software Testing for Beginners · Ready for automation? Playwright + Claude AI course