Software Testing Interview Questions for Junior Roles (₹4–6 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.

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

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

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

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

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

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

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

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

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

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

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 bug is behaviour that deviates from agreed requirements; an enhancement is a new or improved capability beyond the current requirements.

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.

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

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.

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

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

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

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

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

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

Risk-based testing: cover critical user flows, recent changes and high-defect areas first. Clearly communicate the untested risks and get stakeholder sign-off.

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

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

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

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

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.

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

A team meeting at the end of a sprint to discuss what went well, what did not and what to improve next.

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

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

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

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

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

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

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.

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

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

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.

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

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

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

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

Basic operations, division by zero, decimals, large numbers, order of operations, clear and backspace, repeated operations and memory keys.

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

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

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

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

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

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 human error causes a defect in the code, and when that defect is executed it produces a failure visible to users.

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

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

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

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

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

A clear title, steps to reproduce, expected vs actual result, environment/build, severity and priority, and evidence (screenshot, video, logs).

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

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

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

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

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.

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

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.

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