CRED Software Testing Interview Questions & Answers

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

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

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

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

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

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

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

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

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

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

Testing how a system moves between states based on events, for example an order going from placed to paid to shipped to delivered.

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

Rules such as NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY and CHECK that keep data valid and consistent.

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

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

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

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.

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

An epic is a large body of work; stories are user-facing slices of it; tasks are technical work items; bugs are 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 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.

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

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

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.

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.

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

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

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

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

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

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