Software Testing Interview Questions for Architects & Directors (₹40–50 LPA)

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.

SDLC is the full software development life cycle; STLC is the testing life cycle: requirement analysis, test planning, test design, environment setup, execution and closure.

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.

User Acceptance Testing — end users or the client verify that the system meets business needs in a production-like environment before go-live.

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

A language to query databases. Testers use it to verify data saved by the application, prepare test data and check backend results.

Valid login, invalid login, forgot password, locked account and session handling are the main scenarios to cover.

Verification: are we building the product right? (reviews, walkthroughs — no code run). Validation: are we building the right product? (actual testing against user needs).

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.

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

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

Rules such as NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY and CHECK that keep data valid and consistent.

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

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

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.

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

Send page, size, sort and filter parameters, then verify counts, order, boundaries (first, last, empty page) and invalid parameter handling.

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

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

They let testers verify totals and counts per category, such as the number of orders per customer, and compare them with the UI or reports.

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.

Log and track bugs, link them to stories, build dashboards and filters with JQL, manage sprints and generate reports.

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

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

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.

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

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

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

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

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).

Talk to developers and users, explore the product, review similar systems, create notes and mind maps, confirm assumptions and write test cases as you learn.

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.

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

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

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.

The team selects stories for the sprint. QA helps estimate testing effort, clarifies acceptance criteria and flags dependencies and risks.

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

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

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

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

Peer review for clarity, coverage of requirements, correct expected results, test data and traceability, then update and baseline them.

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

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.

Keep tests modular, prioritise by risk, use exploratory testing, automate stable parts and keep close contact with product owners.

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

Prioritising tests by the likelihood and impact of failure, so critical areas get the most coverage when time is limited.

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

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

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

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.

Test on real devices and OS versions, interrupts such as calls, battery, network changes, gestures, permissions and app store guidelines.

A shared checklist for when a story is complete, usually including code review, tests passing, no open critical bugs and documentation updated.

A regular review where QA, development and product assess new bugs and decide severity, priority, owner and target release.

Re-check environment, data, browser and steps; check the logs; try the reporter's setup; add video and console logs; mark it 'cannot reproduce' only after discussing with the developer, and keep monitoring.

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

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

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

Unit, integration, system and acceptance testing, moving from individual components to the complete product in front of users.

Code is built and tested automatically on each change; tests are quality gates that stop faulty builds from moving forward.

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

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

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

The extent of requirements or code exercised by tests. Measure requirement coverage with a traceability matrix and code coverage with tools.

The hardware, software, data and configuration where testing happens, set up to mirror production as closely as practical.

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.

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

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

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

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