Adobe Software Testing Interview Questions & Answers

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

Send page, size, sort and filter parameters, then verify counts, order, boundaries (first, last, empty page) and invalid parameter handling.

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

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

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.

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.

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

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

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

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

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

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.

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

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

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

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.

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

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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.

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

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

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

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

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

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

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

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.

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

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.

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

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

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

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