Apple Software Testing Interview Questions & Answers

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

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

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

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

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

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

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

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.

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

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

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

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

A defect that stops testing or release of a feature because no workaround exists, so it is highest priority.

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

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.

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

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

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

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

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.

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

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

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

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.

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

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

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

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

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.

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

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

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.

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

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

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

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

A regular review where QA, development and product assess new bugs and decide severity, priority, owner and target 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.

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

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

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

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

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

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

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

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

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.

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.

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.

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

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

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.

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

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.

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

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