Oracle Software Testing Interview Questions & Answers

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

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

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

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

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

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

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

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

Positive cases use valid inputs to confirm expected behaviour; negative cases use invalid inputs to confirm the system handles errors gracefully.

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

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.

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

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.

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.

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

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

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.

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.

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

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

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

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

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

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

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

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

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.

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.

Assess impact and risk, discuss with product and dev, decide to fix, defer with a workaround or delay release, and document the decision.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 scenario is a high-level thing to test (user logs in); test cases are the detailed steps and data that verify it.

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

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

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.

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

Use mocks or stubs from the API contract such as Swagger, write test cases early and validate again when the real service is available.

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

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.

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

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

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

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

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.

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

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.

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

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

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.

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

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