Manual Testing
Interview Questions

1

Fundamentals

What is the difference between verification and validation?

Verification asks "are we building the product right?" — checking documents and code against the spec. Validation asks "are we building the right product?" — running the software to confirm it meets real user needs.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

2

Defect Management

What is the difference between severity and priority?

Severity measures how badly a bug damages the system technically; priority measures how urgently the business needs it fixed. They are independent scales, set by different people.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

3

Test Design

What is the difference between a test scenario and a test case?

A test scenario is a one-line description of what to test; a test case is the detailed how — exact steps, data, and expected result. One scenario typically expands into several test cases.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

4

Defect Management

Walk me through the defect (bug) life cycle.

A defect travels through defined states from the moment it is found until it is closed — ensuring nothing slips through unresolved and every stakeholder knows exactly where each bug stands.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

5

Process

What are the phases of the Software Testing Life Cycle (STLC)?

The STLC is the structured sequence of activities QA follows — from understanding requirements through to reporting final results — ensuring testing is planned, executed, and closed in a consistent way.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

6

Test Types

What is the difference between smoke testing and sanity testing?

Smoke testing is a quick, broad check that a new build is stable enough to test at all. Sanity testing is a narrow, focused check that one specific fix or feature works correctly after a…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

7

Test Types

What is the difference between functional and non-functional testing?

Functional testing checks whether the system does what it's supposed to do — the features and business rules. Non-functional testing checks how well it does it — performance, security, usability, and reliability.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

8

Test Types

What is the difference between black-box, white-box, and grey-box testing?

The three terms describe how much internal knowledge a tester has when designing tests. Black-box: none. White-box: full. Grey-box: partial.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

9

Test Design Techniques

What is Boundary Value Analysis (BVA)?

Boundary Value Analysis tests the values at and just outside the edges of a valid range — because that is where off-by-one bugs hide. Testing the middle of a range rarely finds anything new.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

10

Test Design Techniques

What is Equivalence Partitioning?

Equivalence Partitioning groups all possible inputs into classes where every value in the class should produce the same result — then tests one representative value per class instead of all values. Same coverage, far fewer…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

11

Test Types

What is the difference between retesting and regression testing?

Retesting re-runs the same failed test case after a bug is fixed to confirm the specific defect is resolved. Regression testing re-runs a broader set of passing tests to confirm the fix didn't accidentally break…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

12

Test Design

What is positive and negative testing?

Positive testing confirms the system works correctly with valid inputs — the happy path. Negative testing confirms the system handles invalid, unexpected, or boundary-breaking inputs gracefully — without crashing or exposing sensitive information.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

13

Fundamentals

What is the difference between an error, a defect/bug, and a failure?

An error is a human mistake that creates a defect in the code. A defect is the flaw left in the product. A failure is what happens when that defect is triggered and causes the…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

14

Test Design

What makes a good test case, and what are its key components?

A good test case is clear enough that anyone can run it and get the same result — no guessing, no assumptions, no need to ask the person who wrote it.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

15

Defect Management

What information should a good bug report contain?

A good bug report contains enough information that a developer can reproduce the defect without asking the reporter a single follow-up question.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

16

Test Types

What is the difference between alpha and beta testing?

Alpha testing is done in-house by the QA team in a controlled environment before release. Beta testing is done by real end users in the real world on a near-final version to catch issues the…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

17

Test Types

What is User Acceptance Testing (UAT)?

UAT is the final testing phase where the actual business users or client verify that the software meets their real-world needs before accepting it for production use. It answers "does this solve our actual problem?"…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

18

Process

What are entry and exit criteria in testing?

Entry criteria define the conditions that must be met before testing can begin. Exit criteria define the conditions that must be met before testing is considered complete. Together they prevent testing from starting too early…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

19

Test Types

What is the difference between static and dynamic testing?

Static testing examines work products — requirements, designs, code — without running the software. Dynamic testing executes the software and checks whether it behaves correctly.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

20

Fundamentals

What is the difference between QA, QC, and Testing?

QA (Quality Assurance) is process-focused and preventive — building the processes that stop defects being introduced. QC (Quality Control) is product-focused and detective — checking the product for defects. Testing is the hands-on activity within…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

21

Process

What is a test plan, and what does it typically contain?

A test plan is a document that defines the scope, approach, resources, schedule, and success criteria for a testing effort — it answers "what are we testing, how, by whom, and how will we know…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

22

Test Types

What is ad-hoc testing?

Ad-hoc testing is informal, unplanned testing with no test cases, no documentation, and no structured goal — the tester simply explores the application using intuition and experience to find bugs. It is fast and can…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

23

Test Types

What is exploratory testing, and how is it different from ad-hoc testing?

Exploratory testing is simultaneous learning, designing, and executing tests — the tester explores the application with a defined charter (goal), takes notes as they test, and lets each discovery guide the next action. It is…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

24

Process

What is the difference between SDLC and STLC?

The SDLC is the full lifecycle of building software — from requirements through deployment and maintenance. The STLC is the testing-specific set of phases that live inside the SDLC — from test planning through test…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

25

Process

What is a Requirement Traceability Matrix (RTM)?

A Requirement Traceability Matrix is a table that links each requirement to the test cases that cover it — proving that every requirement has at least one test, and instantly revealing any gaps.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

26

Practical

How would you test a login page? Give some test cases.

Testing a login page well means covering five distinct angles — not just the happy path. An interviewer wants to hear you think in categories, not just list random cases.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

27

Practical

You find a critical bug one hour before the release is due to go live. What do you do?

Surface it immediately with full facts — do not stay quiet, and do not make the release decision alone. Your job is to give stakeholders the clearest possible risk picture so they can decide with…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

28

Practical

The build you received for testing keeps crashing every few minutes. How do you handle it?

Document the crash, escalate immediately, and stop testing the unstable build — continuing wastes time and generates false defects that are not real application bugs.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

29

Practical

Walk me through the test cases you would write for a user registration form.

A user registration form has five distinct test categories — an interviewer is listening for whether you cover all of them, not just the obvious happy path.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

30

Defect Management

You log a bug and the developer marks it "Not a Bug" or "Works as Designed." How do you respond?

Investigate first, then present facts — not opinions. If the spec supports your position, share the exact line from the requirement. If it's genuinely ambiguous, escalate to the PM or BA for a ruling.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

31

Practical

How would you test a "forgot password" / password reset feature end to end?

A password reset flow has four distinct test categories — functional, negative, security, and usability — and the security category is the most critical because this feature is a common account takeover attack vector.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

32

Practical

You have just 3 hours to test a new feature before it goes live. What do you do first?

With three hours, prioritise ruthlessly and document your scope — do not spend the first hour writing a test plan, and do not run random tests hoping to cover everything.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

33

Practical

Write test cases for an ATM cash withdrawal.

ATM withdrawal is a classic interview question that tests whether you think in categories — happy path, validation, system state, security, and data integrity. Financial systems must never give money without debiting the account, or…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

34

Defect Management

Give an example of a high-severity but low-priority bug, and a low-severity but high-priority bug.

High severity + low priority: a technically serious crash that affects almost no one or can be worked around. Low severity + high priority: something minor that looks terrible or blocks a critical business moment.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

35

Defect Management

How do you decide whether something is worth raising as a bug?

Ask three questions: does it differ from expected behaviour? Could it affect users or the business? Is it reproducible? If all three are yes — log it. When in doubt, log it and let the…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

36

Defect Management

The same bug keeps reappearing in every release even after it has been marked "Fixed." What do you do?

A recurring bug means the root cause has not been addressed — either the fix is wrong, another change overwrites it, or there is a deeper systemic problem. Stop the cycle and investigate.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

37

Practical

You are new to the team and your first task is to test a feature you know nothing about. How do you start?

Gather context before testing anything — reading requirements, reviewing existing tests, and getting a brief walkthrough from the developer or PM. Testing blind wastes time and produces low-quality results.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

38

Practical

How would you test a notifications feature (email, push, or in-app)?

Notifications look simple but have five distinct failure categories — triggering, content, delivery, preferences, and scale. Many QA engineers only test the happy path (notification arrives with correct content) and miss the rest.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

39

Practical

How would you test a date picker / calendar input field?

Date pickers have far more edge cases than they appear — calendar logic, locale, boundary dates, and keyboard navigation all create unique failure points that happy-path testing misses entirely.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

40

Practical

How would you test a multi-step form (a wizard or stepper)?

Multi-step forms have unique failure points that single-page forms don't — data persistence between steps, navigation edge cases, and duplicate submission are the three most common bug sources.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

41

Practical

How would you test a "delete account" or "cancel subscription" feature?

Destructive and irreversible actions need particularly careful testing — confirmation flow, data handling, security, and edge cases all create distinct failure modes that have real user and legal consequences.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

42

Practical

How would you test an autocomplete / type-ahead search field?

Autocomplete has five test categories — triggering, input variations, performance, accessibility, and edge cases. Performance and accessibility are the two most commonly skipped by junior testers.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

43

Practical

How would you test pagination on a results page?

Pagination has four test categories — navigation controls, data correctness, edge cases, and URL/deep-linking. Data correctness is the most critical: items appearing on two pages or disappearing between pages is a silent data integrity bug.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

44

Practical

A developer just fixed the bug you reported. What do you test beyond just the fix itself?

Retesting the original bug is step one. You also run regression checks on adjacent areas, test related variations of the same feature, and update the ticket with the verified build number.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

45

Practical

How would you test a "Remember Me" / stay logged in feature?

"Remember Me" involves persistent session management — a security-sensitive area with four test categories: happy path, session duration, security (the most critical), and cross-browser behaviour.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

46

Practical

How would you test a profile picture or image upload feature?

Image upload testing has five categories — valid uploads, invalid uploads, image handling, security, and usability. Security is the most commonly missed: a file disguised as an image but containing executable code is a real…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

47

Practical

What would you test on a product detail page of an e-commerce site?

A product detail page has five test categories — content accuracy, product variations, add-to-cart behaviour, non-functional quality, and edge cases. Interviewers use this question to check whether you think beyond the happy path.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

48

Practical

How would you test a form with conditional fields — fields that appear or disappear based on other selections?

Conditional field forms have four test categories — triggering, validation, data persistence, and edge cases. The most common bug is hidden required fields that block submission — a validation message appears for a field the…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

49

Practical

How do you test across multiple environments (dev, staging, production)? What do you watch out for?

Each environment has a different purpose, different tolerance for instability, and different risks — knowing which tests belong in which environment prevents wasted effort and environment-specific false failures.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

50

Practical

How would you test a two-factor authentication (2FA) feature?

Two-factor authentication adds a second verification step after password login — your job is to test every combination of valid, invalid, expired, and reused codes, plus the recovery path.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

1

Test Strategy

You have far more to test than time allows. How do you decide what to test?

When time is short, you use risk-based testing — you rank every area by how likely it is to fail and how badly that failure would hurt, then test the highest-risk areas most deeply.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

2

Test Design Techniques

What is decision table testing, and when would you use it?

Decision table testing is a technique where you map every combination of input conditions to its expected outcome in a grid — so no rule slips through a gap.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

3

Test Design Techniques

What is state transition testing?

State transition testing checks every valid move between a system's states works correctly, and every invalid move is properly blocked.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

4

Test Design Techniques

What is pairwise (all-pairs) testing, and why use it?

Pairwise testing is a technique that ensures every combination of any two input variables is covered at least once — catching the vast majority of combination bugs with a fraction of the test cases that…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

5

Test Design Techniques

What is use case testing?

Use case testing derives test cases from the step-by-step user journeys documented in use cases — covering both the main success flow and every alternate or exception path.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

6

Practical

How do you test a feature when there are no requirements or documentation?

When there are no requirements, you reconstruct the spec from other sources — asking people, exploring the app, comparing similar products — then document your assumptions and test against those.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

7

Regression

You cannot re-run the entire regression suite every release. How do you choose what to run?

You build a layered regression set: a small always-run smoke suite, plus a targeted change-impact layer added on top of it for each release.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

8

Defect Management

A developer says your bug "isn't reproducible" or "works on my machine." How do you handle it?

When a developer can't reproduce your bug, your job is to close the environment gap — not to argue, but to provide every piece of context that might differ between your machine and theirs.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

9

Process

What is the difference between a test strategy and a test plan?

A test strategy defines how an organisation approaches testing at a product or programme level; a test plan is the specific execution plan for one project or release.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

10

Test Types

How do you approach cross-browser and device compatibility testing?

You build a browser/device matrix based on your real user analytics, test the top combinations deeply, and use a cloud device farm like BrowserStack for breadth coverage of the long tail.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

11

Practical

How would you test a search functionality?

Testing search means covering matching accuracy, edge-case inputs, combined filters, security, and performance — not just "type a word and results appear."

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

12

Practical

How would you test a file upload feature?

Testing a file upload means covering valid files, invalid file types and sizes, edge-case filenames, security, and network resilience — not just confirming a normal file uploads successfully.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

13

Practical

How would you test an e-commerce checkout / shopping cart?

Testing e-commerce checkout means covering the full purchase journey — cart management, pricing accuracy, payment scenarios, post-purchase integrity, and the edge cases that cause double charges or lost orders.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

14

Practical

How would you test an API manually, without a UI?

To test an API manually, you use a tool like Postman to send requests directly and verify status codes, response body, error handling, authentication, and side effects — testing the contract, not just a happy…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

15

Strategy

What is the test pyramid, and where does manual testing fit?

The test pyramid is a model for balancing test types: many fast unit tests at the base, fewer integration tests in the middle, and a small number of slow end-to-end tests at the top. Manual…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

16

Metrics

What defect metrics do you track, and what do they tell you?

The four most useful defect metrics are density, leakage, age, and removal efficiency — each reveals a different dimension of quality and process health.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

17

Defect Management

How do you do root cause analysis on a defect?

Root cause analysis means not stopping at the symptom — you keep asking "why" until you reach the underlying cause, then fix that, not just the surface bug.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

18

Test Types

What is usability testing?

Usability testing checks whether real users can complete their tasks quickly, intuitively, and without frustration — it focuses on the human experience, not just whether the software technically functions.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

19

Test Types

What is accessibility testing, and what would you check?

Accessibility testing verifies that people with disabilities — visual, motor, cognitive, or hearing — can use the product, typically guided by the WCAG (Web Content Accessibility Guidelines) standard.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

20

Test Types

What is the difference between localization and internationalization testing?

Internationalisation (i18n) testing checks that the application is built to support multiple languages and regions; localisation (l10n) testing checks that a specific language or region adaptation is correct.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

21

Process

How do you estimate testing effort for a feature?

You break the testing work into concrete tasks — analysis, design, execution, retesting, regression — size each from experience or comparable past features, add setup and buffer, and give a range rather than a false-precision…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

22

Exploratory Testing

How do you make exploratory testing structured and accountable?

You use session-based test management: time-boxed sessions each with a written charter (a specific mission), notes captured during the session, and a debrief report at the end covering what you tested, what you found, and…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

23

Process

It is the day before release and you have not finished testing. What do you do?

You re-prioritise by risk — finish the critical and changed areas first, acknowledge what's been deferred, and communicate the risk picture clearly to stakeholders so the go/no-go decision is made with full information.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

24

Metrics

How do you measure test coverage, and what are its limits?

Test coverage is measured through requirements coverage (every requirement has at least one test, tracked in an RTM) and code coverage (percentage of code lines executed by tests). Its fundamental limit is that it measures…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

25

Defect Management

How do you handle a bug that only happens sometimes (flaky / intermittent)?

You hunt the pattern systematically — capturing every variable (environment, data, timing, sequence, concurrency) each time it occurs — and log what you find even if you can't reproduce it on demand.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

26

Process

When do you decide testing is "done"?

Testing is never provably exhaustive, so "done" is an agreed, risk-based call: you stop when the pre-agreed exit criteria are met, the defect-find rate has flattened, and remaining risks are accepted by stakeholders.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

27

Practical

You have 50 test cases to execute and only 2 days to do it. What is your approach?

You triage and prioritise before you execute a single test — group cases by risk, run the critical ones first, communicate scope risk early, and track progress in real time so blockers surface immediately.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

28

Process

You join a sprint that is already halfway through. How do you get up to speed and contribute quickly?

You actively plug in rather than wait to be handed work — read the board, attend standup, pick up the nearest-to-done stories, and get environment access set up before the first feature lands.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

29

Practical

You discover a Severity-1 bug 2 hours before the deployment window. What do you do?

You reproduce it, escalate immediately with the full picture — steps, impact, workaround options — and let stakeholders make the go/no-go call with full information. This is not a decision you make alone.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

30

Defect Management

A developer tells you your test case is wrong and the feature "works as designed." You still think it's a bug. How do you handle it?

You go back to the written requirement and let the spec settle it — "works as designed" is only valid if the current behaviour actually matches what the requirement says.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

31

Test Strategy

You have 3 features to test but time allows only one full test cycle. How do you decide which gets full coverage?

You apply risk-based prioritisation: rank each feature by business impact, change scope, complexity, and historical fragility — the highest-risk feature gets the full cycle, the others get smoke checks only, and you communicate the trade-off…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

32

Test Types

How do you approach testing a mobile app? What is different compared to web testing?

Mobile testing shares the same functional principles as web testing but adds a layer of device, OS, network, gesture, and permission variables that web testing doesn't have — each of which is a distinct category…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

33

Process

Your test environment goes down and you are told it won't be fixed for 2 days. How do you stay productive?

An environment outage is a forced context switch — you use the time for the work that doesn't need the environment: reviewing requirements, refining test cases, clearing the backlog, and getting ahead of the next…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

34

Process

You are asked to sign off on a release that you haven't fully tested due to time constraints. What do you do?

You document what you tested and what you didn't, give an honest risk assessment with specific risks named, propose mitigations, and let stakeholders make the go/no-go with full information — sign-off means "I tested X…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

35

Regression

Your regression suite keeps failing intermittently and developers have stopped trusting it. How do you fix this?

A suite developers have stopped trusting is worse than no suite — you fix it by quarantining flaky tests immediately, triaging each failure to its root cause, and rebuilding trust through a visible trend of…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

36

Defect Management

Three bugs escaped to production from your last release. How do you run the postmortem?

You run a blameless postmortem: establish the facts, trace the escape path for each bug to its root cause, define specific (not vague) corrective actions, and measure whether leakage reduces in the next release.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

37

Process

How do you estimate testing for a large feature when requirements keep changing?

You give a ranged estimate based on what's known, state your assumptions explicitly, build in a buffer for change cycles, and agree a re-estimate checkpoint once requirements stabilise.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

38

Practical

How would you test a payment gateway integration? Walk through your full approach.

Payment testing covers five areas: functional success/failure paths, security, idempotency, integration integrity (webhooks), and non-functional compliance — in that order of priority.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

39

Practical

How do you test a third-party API integration where you don't control the external service?

You test your side of the integration thoroughly — using the vendor's sandbox and contract mocks — and verify your system handles every error response, timeout, and rate limit gracefully, even when the third party…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

40

Practical

How would you test a reporting or analytics dashboard?

Testing a dashboard means verifying data accuracy first, then filter correctness, edge cases in data (empty, large, negative), performance, and export — in that priority order.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

41

Practical

How would you test a real-time feature like live chat or live price updates?

Real-time feature testing focuses on connectivity resilience, message ordering under concurrent use, edge-case inputs, and security isolation — the failure modes that batch systems don't have.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

42

Practical

How do you test for data integrity when a feature updates records across multiple database tables?

Multi-table update testing verifies that all tables change as expected, partial failures are rolled back completely, referential integrity is maintained, and concurrent updates don't cause silent data loss.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

43

Test Data

The test environment data doesn't reflect real production patterns. How does this affect testing and what do you do?

Unrealistic test data creates false confidence — performance issues, data-pattern bugs, and edge cases that only exist in production get completely missed in testing.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

44

Process

A developer asks you to review their pull request and unit tests before merging. What do you look for?

As a QA reviewing a PR, you look for test coverage against the acceptance criteria, assertion quality, test isolation, and coverage gaps for negative scenarios — not code style or architecture, which belong to developer…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

45

Practical

How would you test a CSV or Excel bulk import feature?

Bulk import testing covers valid files, format and data validation, encoding edge cases, per-row error handling, and clear feedback — because a single bad file can silently corrupt large amounts of data.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

46

Process

How do you approach testing a release that changes the database schema?

Schema change testing covers the migration script, data transformation correctness, application behaviour after migration, performance on realistic data volumes, and a tested rollback — in that order.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

47

Practical

How do you handle test data pollution — other testers or automated runs are corrupting your test environment?

You fix test data pollution at three levels: short-term isolation (dedicated test accounts, timestamped data), medium-term hygiene rules (daily resets, separate environments), and long-term test design (self-contained tests that set up and tear down their…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

48

Practical

How would you test a user permission and role-based access control system?

RBAC testing covers positive access (each role can do what it should), negative access (each role is blocked from what it shouldn't), privilege escalation attempts, boundary cases (role change mid-session), and API-layer enforcement.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

49

Practical

How do you test an application across different time zones, date formats, and DST (Daylight Saving Time)?

Time zone and locale testing covers UTC storage and correct local display, DST boundary events, locale-appropriate date/number formats, and scheduling features that must fire at the user's local time — not the server's.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

50

Practical

How would you approach end-to-end testing of a user journey that spans multiple systems or services?

You map the full system chain first, drive the test from the user's perspective through the top-level interface, focus on the integration seams between systems, and keep the E2E suite lean — covering critical journeys…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

1

Test Strategy

How would you build a test strategy for a brand-new product?

You start from the product's purpose, users, risks, and business goals — not from a template — then define test types, levels, environments, tools, quality gates, and the manual-vs-automation split, keeping it lean and evolving.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

2

Automation

How do you decide what to automate and what to keep manual?

The decision is ROI-based: automate what's stable, repetitive, and run frequently; keep manual what requires human judgement, changes rapidly, or costs more to automate than the automation saves.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

3

Agile

How does QA work within an Agile / Scrum team?

In Agile, QA is embedded in the team as a continuous collaborator — not a gate at the end. QA involves itself from story refinement, tests continuously as features land, automates alongside development, and treats…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

4

Strategy

What is shift-left testing (and shift-right)?

Shift-left means moving testing earlier in the development cycle — into requirements and design — so defects are caught when they're cheapest to fix. Shift-right means testing later, in production, to catch issues that only…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

5

Release Management

How do you make a go/no-go release decision when there are still open defects?

For each open defect you assess severity, business impact, and whether a workaround exists — then give a clear, data-backed recommendation. The final call is the business's; QA supplies the honest risk picture.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

6

Quality

Bugs keep slipping to production. How do you reduce defect leakage?

You run root-cause analysis on the escaped defects to find patterns, then systematically strengthen the weak points: shift-left early detection, targeted coverage gaps, tighter quality gates, and production monitoring to catch what slips through.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

7

Incident Management

A critical bug reached production that testing missed. How do you respond?

You contain the incident first, run a blameless root-cause analysis focused on why testing missed it, then prevent recurrence by fixing the specific process gap and adding a test that would have caught it.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

8

Leadership

How do you mentor junior testers and raise the whole team's quality?

You develop junior testers by pairing on test design, giving specific feedback on their output, teaching the reasoning behind techniques rather than just the steps, and progressively giving them ownership so they grow into independent…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

9

Test Strategy

How do you apply risk-based thinking when planning testing for a whole project?

You identify risk areas with the team, score each by likelihood × impact, allocate testing depth proportional to risk, document the assessment, and revisit it as the project evolves.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

10

Process Improvement

You join a team whose QA isn't catching bugs. How do you improve it?

You diagnose before prescribing: analyse the patterns in escaped defects, map the current process, identify the biggest gaps, make one targeted change at a time, and measure whether leakage trends down.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

11

Process

How do you define quality gates or a Definition of Done for QA?

You define quality gates as a set of explicit, objective, agreed criteria that a feature must meet before it advances — making "done" unambiguous so half-tested work can't quietly slip through.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

12

Test Data

What is your strategy for test data management?

Test data is a first-class asset: it must be realistic, sufficient, repeatable, and safe (no real PII). Your strategy covers how data is created, seeded, refreshed between runs, and designed to include the edge cases…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

13

CI/CD

What is QA's role in a CI/CD pipeline?

QA owns the testing gates in the pipeline: defining which tests run at which stage, ensuring those gates are reliable, and adding monitoring and rollback paths so defects fail fast rather than reaching production.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

14

Metrics

Which QA metrics actually matter, and which are vanity metrics?

The metrics that matter are outcome-focused: defect leakage, defect removal efficiency, severity of escapes, and time-to-detect. Vanity metrics measure activity that's easy to inflate without improving quality: raw test-case count, bugs logged per sprint, and…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

15

Collaboration

A developer or PM disagrees with the severity you assigned a bug. How do you handle it?

You explain the user impact, frequency, and affected scenarios with data, listen to their context, and keep severity (technical judgement) separate from priority (business decision) — the goal is the right outcome, not winning the…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

16

Regression

Your regression suite has grown huge and slow. How do you keep it manageable?

You treat the regression suite as a product that needs maintenance: prune the dead weight, tag tests by risk tier for targeted runs, parallelise execution, and fix or quarantine flaky tests so the suite earns…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

17

Architecture

How would you approach testing a microservices-based system?

You test microservices at four layers: each service in isolation, service-to-service interactions via contract testing, a small set of critical end-to-end journeys, and resilience (what happens when a downstream service fails or goes slow).

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

18

Quality Culture

How do you build a culture where quality is everyone's responsibility, not just QA's?

You shift the team from "throw it over the wall to QA" to shared ownership: QA joins early, developers own their unit tests, defects are visible to the whole team, and prevention is celebrated more…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

19

Tooling

How do you decide whether to adopt a new testing tool or process?

You start from the specific problem you're solving — not the shiny tool — define success criteria upfront, run a time-boxed pilot on a real use case, evaluate fit against your stack and team, and…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

20

Non-functional

How do you own the non-functional testing strategy (performance, security, accessibility)?

You treat non-functional requirements as first-class: define explicit, measurable targets up front, plan when and how each is tested, use appropriate tools and specialists, and bake them into the pipeline and acceptance criteria — not…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

21

Metrics

How do you measure whether your testing itself is effective?

You measure testing effectiveness by outcomes: defect removal efficiency, leakage trend, severity of escapes, and time-to-detect — and pair the numbers with a qualitative check: are we testing the right risks?

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

22

Strategy

How do you test safely in production?

You use controlled techniques that limit the blast radius — feature flags, canary deployments, synthetic monitoring, and strong observability with a fast rollback plan — to catch real-world issues that staging can't replicate while keeping…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

23

Leadership

How do you balance release speed against quality, and when do you push back?

You make risk visible so the business can decide with eyes open — low-risk changes can move fast; high-risk areas need slowing down. When you push back, you do it with data (cost of a…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

24

Agile

Requirements keep changing mid-project. How do you keep testing effective?

You design your testing approach to absorb change rather than resist it, so every requirement shift doesn't trigger a full rework of your test assets.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

25

Leadership

You are the first QA hire for a new team/product. How do you set up QA from scratch?

You start by learning before building — understand the product's risk profile and current informal practices before introducing any process or tooling.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

26

Planning

How do you estimate and plan QA capacity across several projects at once?

You allocate QA time by risk and business priority — not by splitting it equally across projects — and you make capacity constraints explicit rather than silently stretching thin.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

27

Leadership

Your manager asks you to cut testing time by 50% for the next sprint. How do you respond?

You don't say yes or no immediately — you quantify what the cut means in terms of specific untested areas and business risk, then present options so the business can decide with full visibility.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

28

Metrics

How do you present QA status and metrics to non-technical stakeholders or leadership?

You translate testing facts into business language — leadership needs to know release risk and what decisions to make, not how many test cases ran.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

29

Automation

Your automated regression suite is failing consistently in CI and the team has stopped trusting it. What is your plan?

A suite the team has stopped checking is worse than no suite — you treat it as a credibility crisis, triage every failure, and rebuild trust from a small reliable baseline rather than trying to…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

30

Incident Management

Three Severity-1 bugs reached production in the last release and leadership is asking questions. How do you handle it?

You follow a contain-learn-prevent sequence: first support the immediate fix, then run a blameless postmortem to find the escape route, then take specific measurable actions so each bug cannot recur undetected.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

31

Leadership

Your QA team has low morale — testers feel their bugs get deprioritised and their work undervalued. What do you do?

You address it as both a visibility problem and a structural problem — testers need to see their work landing and need to be involved early enough that their input actually shapes outcomes.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

32

Release Management

A PM is strongly pushing to release a feature you believe carries significant untested risk. How do you handle it?

You make the risk explicit and documented, present options with a clear recommendation, and ensure the decision is made with full visibility — not absorbed silently or blocked outright.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

33

Automation

You need to build a test automation strategy from scratch for a team that has never automated before. Where do you start?

You start with people and problems — not tools — and prove value on a small high-confidence area before expanding anywhere else.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

34

Test Strategy

How do you test a feature that involves AI or machine learning output?

AI/ML testing is different because there is no single correct answer — you are testing a probabilistic system against defined quality thresholds, not exact expected values.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

35

Leadership

You manage 3 QA engineers with very different skill levels. How do you allocate work and develop each of them?

You match work to each person's current skill level and growth edge — not just who is available — and you use the work itself as the development vehicle rather than relying only on separate…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

36

Process

Your team is moving from monthly releases to 2-week sprints. How does QA adapt?

Moving to 2-week sprints isn't just a schedule change — it forces QA to shift from a sequential "test after handover" model to fully parallel, shift-left testing where test design starts before code does.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

37

Quality

Business pressure consistently overrides quality gates. Features ship with known bugs repeatedly. How do you change this?

This is a systemic and cultural problem that individual conversations cannot fix — you attack it by making the cost of escaping bugs financially visible, automating gates so they cannot be casually overridden, and requiring…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

38

Process

How do you approach testing in a regulated industry (finance, healthcare, pharma) where every defect needs full traceability?

Regulated testing is not fundamentally different in what you test — it is different in the rigour with which you document, trace, and prove everything. The core mindset is: if it isn't documented, it didn't…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

39

Leadership

How do you build a QA knowledge-transfer process so quality doesn't drop when a key tester leaves the team?

You reduce the bus factor by ensuring no test area has a single point of knowledge — through living documentation, a primary/secondary ownership model, deliberate cross-training, and automation that encodes institutional knowledge in code.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

40

Metrics

How do you measure and demonstrate the ROI of test automation investment to leadership?

You frame the ROI in the terms leadership actually cares about — time saved, cost avoided, and defects prevented — not technical metrics like test count or coverage percentage.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

41

Architecture

How do you approach contract testing in a microservices architecture?

Contract testing defines the agreed interface between two services and verifies both sides honour it — catching integration breaks in the CI of each service before they ever reach a shared environment.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

42

Test Types

As a QA lead, what do you own in security testing versus what a dedicated security team owns?

QA owns the security hygiene embedded into every feature test cycle — OWASP basics, access control checks, data exposure. The dedicated security team owns deep exploitation, infrastructure, formal pentests and certifications.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

43

Test Strategy

How do you ensure testing stays effective after a major technology migration — new platform, framework, or cloud move?

You run the full test suite before the migration to establish a baseline, run tests in parallel against both environments during the transition, and treat every new failure after cutover as either a test that…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

44

Automation

You are brought in to review and improve an existing test automation framework. What is your approach?

You assess the current state before changing anything — run the suite, read the architecture, talk to the team — then fix in order of impact: stability first, CI integration second, refactoring third.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

45

Quality

How do you balance paying down test automation technical debt against delivery pressure?

You make the debt visible in concrete cost terms, negotiate a regular time allocation rather than a one-off sprint, and fix opportunistically in parallel — never letting new work add more debt while old debt…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

46

CI/CD

How do you design an on-call and production monitoring strategy that QA contributes to?

QA's role doesn't end at deployment — shift-right means QA defines what to monitor in production, sets alerting thresholds from a user impact perspective, owns synthetic transaction monitors, and feeds every incident back into the…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

47

Architecture

How do you design a testing strategy for a complete platform migration — monolith to microservices?

A monolith-to-microservices migration is one of the highest-risk engineering changes a team makes — the testing strategy runs in four phases: baseline, parallel validation during extraction, integration seam testing, and post-migration production monitoring.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

48

Quality

How do you establish shared quality ownership with developers — shifting quality left rather than leaving it all to QA?

Shared quality ownership is built through structural changes first — testable acceptance criteria before development, developer-owned unit tests in the DoD, and joint retrospectives on escaped defects — not through announcements that "quality is everyone's…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

49

CI/CD

How do you manage QA in a team using continuous deployment — code ships to production multiple times a day?

Continuous deployment eliminates the traditional "testing phase" — QA shifts entirely to pre-code quality gates, fast automated pipelines, feature-flag-based testing, and production observability as the live quality signal.

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →

50

Test Strategy

How do you design a testing strategy for a system that processes real-time financial transactions?

Financial transaction systems require a test strategy spanning functional correctness (to the decimal), idempotency and atomicity, concurrency and race conditions, failure recovery, security, and a complete audit trail — because every failure mode here directly…

↳ Includes walked-through example, real-world QA scenario & rule of thumb

Get the full answer on QAVeda →