Infosys Software Testing Interview Questions & Answers

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.

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

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.

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

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

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

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

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 defect that stops testing or release of a feature because no workaround exists, so it is highest priority.

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.

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

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

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.

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

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

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

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

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.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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.

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.

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

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

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

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

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

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.

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.

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

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

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.

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

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

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.

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

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

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

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

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

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

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.

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

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.