Accenture Software Testing Interview Questions & Answers

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.

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

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

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

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

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.

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.

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.

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

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

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.

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.

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

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

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

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

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

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

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

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

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.

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

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

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.

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

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

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

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

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

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

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

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

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.

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

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

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

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

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.

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

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.

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.

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.

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.

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

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

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.

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 document defining scope, approach, resources, schedule, entry and exit criteria, risks and deliverables of testing.

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