QA interview
QA interview questions with answers
The questions QA engineers are asked most often, with clear answers, plus a 30-question test. Score 75% or more and you pass our practice interview.

Can you pass a QA interview?
30 random questions from our question bank. Answer at least 75% correctly to pass.
- 30 questions, one correct answer each
- You see the explanation after every answer
- 75% or more — you pass the interview
- A new random set every time you start
Questions and answers
Grouped by topic. Click a question to see the answer.
Testing fundamentals
What is software testing and why do we need it?
Testing is evaluating a product to find defects and to give the team information about its quality. It reduces the risk of failures in production, protects users and the business, and helps decide whether a release is ready.
Testing can show that defects exist, but it can't prove that there are none.
What is the difference between QA, QC and testing?
QA (quality assurance) is process-oriented and preventive: good practices, reviews and standards that stop defects from appearing. QC (quality control) is product-oriented: checking that what was built meets requirements. Testing is the main QC activity: running or examining the software to find problems.
What is the difference between verification and validation?
Verification answers “are we building the product right?” — does it match the specification. Validation answers “are we building the right product?” — does it meet the real user need.
What is the difference between an error, a defect and a failure?
A person makes an error (mistake). It results in a defect (bug) in code or documentation. When the defect is executed, it may cause a failure — observable incorrect behaviour.
Name the seven principles of testing.
Testing shows the presence of defects; exhaustive testing is impossible; early testing saves time and money; defects cluster together; tests wear out (pesticide paradox); testing is context-dependent; absence of errors is a fallacy.
Types and levels
What testing levels do you know?
Unit (component), integration, system and acceptance testing. They differ in scope: from one function to the whole product checked by the business or users.
What is the difference between smoke, sanity and regression testing?
Smoke is a quick check that a new build is stable enough to test at all. Sanity is a narrow check that a specific change or fix works. Regression checks that changes didn't break functionality that worked before.
What is the difference between re-testing and regression testing?
Re-testing (confirmation testing) checks that a specific fixed bug is really fixed. Regression testing checks that the fix or other changes didn't break anything else.
Black box, white box and grey box — what's the difference?
Black box: testing through inputs and outputs without knowledge of the code. White box: tests designed from the internal structure of the code. Grey box: partial knowledge, for example of the database or API, used to design better black-box tests.
What is functional and non-functional testing?
Functional testing checks what the system does (business rules, calculations, workflows). Non-functional testing checks how well it does it: performance, security, usability, compatibility, reliability.
What is exploratory testing?
Simultaneous learning, test design and execution, guided by a charter and a time box. It is great for finding unexpected problems in new or poorly specified features and complements scripted testing.
Test design
Explain equivalence partitioning and boundary value analysis.
Equivalence partitioning splits inputs into groups the system should treat the same and tests one value per group. Boundary value analysis tests values on and next to the edges of those groups, where off-by-one errors happen. For an age field 18–65 we test 17, 18, 65 and 66 plus invalid partitions.
When would you use a decision table?
When the result depends on a combination of several conditions, for example a discount that depends on order total, membership and delivery type. Each column (rule) becomes a test case, and gaps in requirements become visible.
What is state transition testing?
A technique for objects with a life cycle (orders, accounts, subscriptions). We test valid transitions between states and check that invalid ones (e.g. shipping an unpaid order) are blocked.
What is pairwise testing?
A combinatorial technique that covers every pair of parameter values instead of every full combination. It dramatically reduces the number of tests for configurations while catching most interaction defects.
How would you test a login form?
Valid login; wrong password and unknown email (without revealing which is wrong); empty fields; boundary lengths; special characters and spaces; case sensitivity; account lockout after N attempts; “remember me” and session expiry; password reset; brute-force protection; HTTPS; keyboard-only and screen reader use; behaviour on mobile and slow networks.
Documentation and bugs
What is the difference between a test plan and a test strategy?
A test strategy describes the general approach to quality for a product or company and changes rarely. A test plan describes scope, approach, resources, schedule, risks and entry/exit criteria for a specific project or release.
Checklist or test case — when to use which?
Checklists are short and flexible, good for experienced testers and fast-changing products. Test cases contain exact steps, data and expected results — good for complex logic, regulated domains, onboarding and automation.
What should a good bug report contain?
A clear title, environment, preconditions, minimal numbered steps, expected and actual results, evidence (screenshots, video, logs), severity, priority and frequency.
What is the difference between severity and priority?
Severity is the impact of a defect on the system. Priority is how urgently it must be fixed. A typo in the company name on the homepage is low severity but high priority; a crash in a rarely used legacy report may be high severity but low priority.
Describe the bug life cycle.
New → Assigned → In progress → Fixed → Retest → Verified → Closed. A bug can be Reopened if it reappears, or Rejected / Deferred / Duplicate depending on the team's decision.
Web and API
What happens when you type a URL into the browser?
DNS resolves the domain to an IP address; the browser opens a TCP/TLS connection; sends an HTTP request; the server (often via CDN and load balancer) returns a response; the browser parses HTML, loads CSS, JS and images, and renders the page, often making further API calls.
What is the difference between GET and POST? What does idempotent mean?
GET reads data and shouldn't change state; parameters are in the URL. POST sends data to create or process something in the request body. An idempotent request gives the same result when repeated: GET, PUT and DELETE are idempotent, POST usually is not.
Name the main HTTP status code classes.
1xx informational, 2xx success (200, 201, 204), 3xx redirects (301, 302), 4xx client errors (400, 401, 403, 404, 409, 429), 5xx server errors (500, 502, 503).
What is the difference between authentication and authorisation?
Authentication verifies who the user is (login, password, token). Authorisation decides what that user is allowed to do. A typical authorisation bug: changing an ID in the URL shows another user's data.
How would you test a REST API?
Check status codes and response schemas; positive and negative inputs; required fields, types and boundaries; authentication and roles; idempotency; pagination and filtering; error messages; performance. Tools: Postman, curl, automated tests with REST Assured, pytest or Playwright.
Process and automation
Where does QA fit in Scrum?
QA is part of the development team: helps refine stories and acceptance criteria, estimates testing effort, tests stories during the sprint, keeps regression up to date and makes quality status visible in reviews and retrospectives.
What would you automate first?
Stable, high-value, frequently repeated checks: smoke tests, critical user journeys, API and business-logic tests, data-driven tests. Not one-off checks, unstable features or things that need human judgement.
What is a flaky test and how do you fix it?
A test that passes and fails without code changes. Common causes: fixed waits, brittle selectors, shared test data, order dependency, unstable environments. Fix with explicit waits for conditions, stable selectors, isolated data and mocking external services.
Situational questions
A developer says “it's not a bug, it's a feature”. What do you do?
Check the requirements and acceptance criteria. If they're unclear, involve the product owner — they decide expected behaviour. Discuss facts and user impact, not opinions, and document the decision.
The release is tomorrow and you found a critical bug. What do you do?
Report it immediately with clear steps and impact, inform the team lead and product owner, help assess the risk and possible workarounds. The decision to release or postpone belongs to the team and business, but it must be made with full information.
How do you test a feature without requirements?
Ask questions to the product owner and developers, study similar features and competitors, use common sense and user expectations, do exploratory testing, and write down assumptions so they can be confirmed.
Request
Interested in our services?
Tell us about your project: a website, a game, an AI feature or something that needs testing. We'll reply with questions or a first proposal.
- Free first consultation
- Reply within 1–2 working days
- Clear plan, timeline and estimate
Prefer email? Write to us directly:
[email protected]