Software Testing Interview Questions for Associate Roles (₹6–8 LPA)

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 development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.

A set of steps with inputs and expected results. Components: ID, title, preconditions, steps, test data, expected result, actual result and status.

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

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

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

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.

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

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

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.

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

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

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

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

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

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

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

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.

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.

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

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

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

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

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

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

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

Testing how a system moves between states based on events, for example an order going from placed to paid to shipped to delivered.

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

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

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

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.

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

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.

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

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

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

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

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

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

Evaluating software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after 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.

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.

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

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

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

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

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

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.

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

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

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

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

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.

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

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

Valid login, wrong password, empty fields, case sensitivity, max length, SQL-injection strings, password masking, 'remember me', lock-out after N attempts and the forgot-password link.