Meta Software Testing Interview Questions & Answers

Verifying the application works across different hardware, software and settings combinations.

200 OK, 201 Created, 204 No Content, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 500 Internal Server Error.

Verify inserted, updated and deleted rows match UI actions, check constraints, duplicates, NULLs and totals with COUNT and SUM queries.

Finding why a defect was introduced, such as unclear requirements or missed reviews, to prevent similar defects in future.

State the problem, location and condition briefly, for example 'Checkout button disabled after applying a coupon on the cart page'.

New → Assigned → Open → Fixed → Retest → Verified → Closed, with Reopened, Rejected, Deferred and Duplicate as side paths.

GET retrieves data and has parameters in the URL; POST sends data in the body to create or process something.

A suite is a collection of related test cases; a run is one execution of a set of tests against a build.

A technique that tests all pairs of input values instead of every combination, greatly reducing test cases while catching most defects.

Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.

Smoke tests run on every build for quick feedback; full regression runs less often, such as nightly or before release.

Use mocks or stubs from the API contract such as Swagger, write test cases early and validate again when the real service is available.

Learning, test design and execution at the same time, without scripted cases — time-boxed sessions with a charter (e.g. 'explore checkout with coupons'), noting bugs and ideas. Great for finding edge cases.

Defects found after release that testing should have caught; leakage % = defects in production / total defects x 100.

Check access with valid, expired and missing tokens, role-based permissions, error codes and that sensitive data is never exposed.

Status code, response body and schema, headers, response time, error messages for invalid input, authentication (401/403) and that data is saved in the database.

By business criticality, usage frequency, defect history, risk and dependencies, running high-priority cases first.

An urgent patch released outside the normal schedule to fix a critical production defect, followed by regression testing and merge back to the main branch.

A development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.

Re-check the requirement, reproduce with clear steps and evidence (screenshots, logs), discuss with the BA/PO and record the final decision.

A document defining scope, approach, resources, schedule, entry and exit criteria, risks and deliverables of testing.

Create a request with method, URL, headers and body, send it, check status and body, add test scripts and save it in a collection.

The number of defects per size of software, for example defects per thousand lines of code or per module, used to compare quality.

INNER returns matching rows, LEFT keeps all left rows, RIGHT keeps all right rows and FULL keeps all rows from both tables.

Valid card and PIN, wrong PIN, three failed attempts, amount above balance, amount above daily limit, invalid denomination, machine out of cash, network failure and receipt printing.

A grid mapping requirements to test cases and defects, proving every requirement is tested.

A defect that stops testing or release of a feature because no workaround exists, so it is highest priority.

Moves to the chosen floor, doors open and close, door sensor stops closing on obstruction, overload alarm, emergency button, behaviour in a power cut, max capacity and the floor display.

Black box tests behaviour without code knowledge; white box tests internal logic and paths; grey box uses partial knowledge of the internals.

Evaluating software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after release.

A bug is behaviour that deviates from agreed requirements; an enhancement is a new or improved capability beyond the current requirements.

Sprint planning (estimate test effort), daily stand-up (status and blockers), sprint review (demo) and retrospective (improve). Testers clarify acceptance criteria early and test within the sprint.

Static testing reviews documents and code without executing; dynamic testing executes the software to observe behaviour.

Mandatory fields, email format, password rules, duplicate email, terms checkbox, captcha, confirmation email and field length limits.

Testing at the edges of input ranges, such as 17, 18 and 19 for an age limit of 18, since errors cluster at boundaries.

List conditions and actions in a table and cover every combination of conditions (rules) — ideal for business rules like loan approval: salary > X AND credit score > Y → approve.

Checking the application works across browsers, devices, operating systems, screen sizes and network conditions.

Internationalisation tests that the product can support many languages and formats; localisation tests that a specific locale is correct for text, currency, date and layout.

Measuring speed and stability: load (expected users), stress (beyond limits), spike (sudden surge), endurance (long duration) and scalability testing.

A model with many fast unit tests at the base, fewer API or integration tests in the middle and a small number of UI tests at the top.

A final document summarising what was tested, defects found and open, metrics, lessons learned and the recommendation for release.

Add, remove, update quantity, price and tax calculation, coupon codes, stock limits, cart persistence after login and checkout navigation.

Designing tests from user flows described in use cases to verify complete real-world interactions.

Testing shows presence of defects, exhaustive testing is impossible, test early, defects cluster, the pesticide paradox, testing is context-dependent and absence-of-errors is a fallacy.

Using experience to guess where defects likely hide, such as empty fields, special characters or unexpected sequences, and designing tests for them.

Alpha is done in-house by internal teams before release; beta is done by a limited group of real users in their own environment.

Positive cases use valid inputs to confirm expected behaviour; negative cases use invalid inputs to confirm the system handles errors gracefully.

Statuses like To Do, In Progress, In Review, Ready for QA, Done and Reopened, with transitions that depend on the team's configuration.

Evaluating how easy and pleasant a product is to use by observing real users complete tasks and noting confusion.

Assess impact and risk, discuss with product and dev, decide to fix, defer with a workaround or delay release, and document the decision.

Break the work into modules and test cases, use past velocity or three-point estimation (optimistic, likely, pessimistic), add time for test data, environment issues, retesting and regression, and keep a risk buffer.

A scenario is a high-level thing to test (user logs in); test cases are the detailed steps and data that verify it.

Test 17, 18, 19, 59, 60 and 61.

DELETE removes selected rows and can be rolled back; TRUNCATE quickly removes all rows and resets the table.

Reproduce and assess impact, inform stakeholders, help developers fix and verify in staging, run regression and check monitoring after the hotfix, then do a post-mortem.

Check SQL injection, brute-force lockout, password masking, session timeout, HTTPS, cookie flags, error messages not revealing users and password reset flow.

Severity is impact on the system; priority is urgency of the fix. A crash in a rare report is high severity, low priority; a spelling mistake in the logo is low severity, high priority.

Success, failure and pending flows, timeouts, refunds, double-click payments, every method (UPI, cards, net banking), rounding, security (no card data stored) and reconciliation with bank reports.

JIRA Query Language, used to search issues, for example project = ABC AND status = Open AND priority = High.

Entry criteria are conditions that must be met to start testing (build ready, environment set); exit criteria define when testing can stop (pass rate, no critical defects).

Scope (in and out), objectives, approach, environments, schedule, roles, entry/exit criteria, risks and mitigation, deliverables and tools.

Clear, concise, independent, repeatable, traceable to a requirement, with precise expected results and tested data.

Testing that is continuous and collaborative within each sprint, with testers working alongside developers and product owners from the start.

For a field accepting 1–100: valid class 1–100 (test 50), invalid below 1 (test −5), invalid above 100 (test 150). One value represents each class.

Severity = impact on the system. Priority = urgency to fix. Logo misspelt on the homepage → low severity, high priority. Crash in a rarely used report → high severity, low priority.

An epic is a large body of work; stories are user-facing slices of it; tasks are technical work items; bugs are defects.

A human error causes a defect in the code, and when that defect is executed it produces a failure visible to users.

Test execution rate, pass percentage, defect density, defect leakage, defect rejection ratio, requirement coverage and automation coverage.

Re-testing existing features after a change. Automate stable, repetitive, high-value flows that run every release.

The observation that a small number of modules contain most defects, so testing should focus on those areas.

Valid transfer, insufficient balance, daily limit, wrong beneficiary, OTP failure, network drop mid-transaction, duplicate click and statement update.

Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.

An API style using HTTP methods on resources identified by URLs, usually exchanging JSON and staying stateless.

Functional testing checks what the system does (login, checkout). Non-functional testing checks how well it does it (performance, security, usability, compatibility).

TDD writes unit tests before code to drive design; BDD describes behaviour in business language scenarios that become automated acceptance tests.

The inputs used in tests. Prepare using valid, invalid and boundary values from production-like but masked data, spreadsheets or generators.

Shift left with early reviews, improve test design, automate regression, use better test data, add monitoring and learn from escaped defects.

Valid keyword, partial match, no results, special characters, very long text, empty search, case sensitivity, spelling errors, suggestions and speed of results.