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

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

An epic is a large body of work; stories are user-facing slices of it; tasks are technical work items; bugs are defects.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

Testing services directly without the UI, checking status codes, responses, security and performance. It finds issues early and is faster than UI tests.

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

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.

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

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

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

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

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.

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

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

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

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.

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

Evaluating software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after release.

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

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.

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

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

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

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

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

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

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 suite is a collection of related test cases; a run is one execution of a set of tests against a build.

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

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

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

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.

Sprint planning (estimate test effort), daily stand-up (status and blockers), sprint review (demo) and retrospective (improve). Testers clarify acceptance criteria early and test within the sprint.

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

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

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

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.

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

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.

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

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