TCS Software Testing Interview Questions & Answers

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

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

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

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.

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

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

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

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.

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.

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

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

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

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

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

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.

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

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

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 services directly without the UI, checking status codes, responses, security and performance. It finds issues early and is faster than UI tests.

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

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

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

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

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

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

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

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

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

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

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.

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

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

Smoke testing checks that the critical features of a new build work (broad and shallow). Sanity testing checks that a specific fix or area works after a change (narrow and deep).

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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