Skip to content
Software Testing
All courses OffersPlacement Report
‹ Back to previous sectionCourse homeAll page URLs

Software Testing Rapid-Fire Questions & Answers

50 questions for the rapid-fire stage — 28 easy, 22 medium.

About the rapid-fire round

Rapid-fire questions are quick definitions and one-line answers that interviewers fire at the start or end of a round to check your Software Testing basics. Aim to answer each in under 20 seconds.

Tips for the rapid-fire round

  • Answer in one or two sentences, then stop.
  • If you don't know, say so quickly and move on; don't guess at length.
  • Revise these the morning of the interview.
  • Practise with a friend who reads them in random order.
Solved — rapid-fireStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
01

How do you test battery and memory usage of a mobile app?

Mobile TestingMedium
Save to ▾
Show answer
Run typical user sessions on a real device and measure battery drain, CPU and memory with platform profiling tools or the device's battery statistics. Compare with the previous version. Look for background work continuing after the app is closed, GPS left on, frequent network polling and memory that keeps growing, which signals a leak. Test on low-RAM devices too, where the OS kills heavy apps quickly.
02

What are the levels of testing?

Testing TypesEasy
Save to ▾
Show answer
Unit, integration, system and acceptance testing, moving from individual components to the complete product in front of users.
03

Why are hard-coded sleeps bad in automated tests?

Automation Basics for Manual TestersEasy
Save to ▾
Show answer
A fixed sleep, such as waiting five seconds, is either too long, which makes the suite slow when the page loads in one second, or too short, which makes the test fail when the server is slow. Both waste time and cause flaky results. Instead, wait for a real condition: an element to appear, a network response to finish or a loading spinner to disappear. Modern tools do much of this automatically.
04

What is defect age?

Bug Life Cycle and JiraMedium
Save to ▾
Show answer
Defect age is how long a defect stays open, measured either in time, from the date it was logged to the date it was closed, or in phases, from the phase where it was introduced to the phase where it was found. High defect age signals slow fixing or triage. Phase-based age shows how late defects are caught; a requirement defect found in UAT has a high age and is costly.
05

What is the testing pyramid?

Testing TypesMedium
Save to ▾
Show answer
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.
06

What is interrupt testing in mobile apps?

Mobile TestingEasy
Save to ▾
Show answer
Interrupt testing checks how the app behaves when something interrupts it: an incoming call, SMS, notification, alarm, low battery warning, network change, plugging in a charger or switching to another app. The app should pause correctly, keep the user's data and resume where the user left off. For example, a call during a payment must not cause a double charge or lose the transaction state.
07

What is defect removal efficiency?

Bug Life Cycle and JiraMedium
Save to ▾
Show answer
Defect removal efficiency shows how many defects the team found before release. DRE = defects found before release divided by (defects found before release plus defects found after release), multiplied by 100. If QA found 90 bugs and users reported 10, DRE is 90 percent. A falling DRE means testing is missing more defects, and the escaped bugs should be analysed to improve test coverage.
08

What is Agile testing?

Agile, SQL and API TestingEasy
Save to ▾
Show answer
Testing that is continuous and collaborative within each sprint, with testers working alongside developers and product owners from the start.
09

What are the seven principles of testing?

Manual Testing BasicsMedium
Save to ▾
Show answer
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.
10

What is the difference between ad hoc testing and monkey testing?

Testing TypesEasy
Save to ▾
Show answer
Ad hoc testing is informal testing without test cases, done by a tester who understands the application and tries likely weak areas based on experience. Monkey testing gives random inputs and actions, often without knowing the application, to see if it crashes. Ad hoc testing is targeted and good at finding logical bugs, while monkey testing is good at finding stability issues and is often automated.
11

What is the difference between HTTP 401 and 403?

Agile, SQL and API TestingEasy
Save to ▾
Show answer
401 Unauthorized means the request has no valid authentication, such as a missing, expired or wrong token, so the client should log in again. 403 Forbidden means the user is authenticated but does not have permission for that resource, such as a normal user calling an admin API. Testers verify both: call without a token to expect 401, and call with a low-privilege token to expect 403.
12

What do you do in the test execution phase when a test fails?

STLC and Test PlanningEasy
Save to ▾
Show answer
Re-run the test once to confirm the failure and rule out wrong data or environment issues. Capture evidence such as screenshots, logs and the build number. Check for an existing bug, then log a new one with clear steps and link it to the test case. Mark the test as failed, and mark dependent tests as blocked if they cannot run. After the fix, retest and run related regression.
13

What should a tester verify about HTTPS on a website?

Performance and Security BasicsEasy
Save to ▾
Show answer
Check every page and API uses HTTPS, and plain HTTP redirects to HTTPS. Verify the certificate is valid, not expired, and matches the domain, with no browser warnings. Look for mixed content, where an HTTPS page loads scripts or images over HTTP. Check login and payment forms submit only over HTTPS and that cookies holding session data have the Secure flag.
14

Why is orientation and screen size testing important?

Mobile TestingEasy
Save to ▾
Show answer
Mobile users have many screen sizes, resolutions, notches and foldable screens, and they rotate their phones. Rotation can recreate the screen and lose entered data if not handled. Test portrait and landscape on key screens, small and large phones and tablets, and check text does not cut off, buttons stay reachable and the keyboard does not hide input fields. Check entered form data survives rotation.
15

Difference between black box, white box and grey box testing?

Manual Testing BasicsEasy
Save to ▾
Show answer
Black box tests behaviour without code knowledge; white box tests internal logic and paths; grey box uses partial knowledge of the internals.
16

What is a test scenario for the login functionality at a high level?

Test Case DesignEasy
Save to ▾
Show answer
Valid login, invalid login, forgot password, locked account and session handling are the main scenarios to cover.
17

What is WCAG and what are its conformance levels?

Accessibility & Usability TestingEasy
Save to ▾
Show answer
WCAG, the Web Content Accessibility Guidelines from the W3C, is the main standard for making web content usable by people with disabilities. The current version is WCAG 2.2. It has three conformance levels: A is the minimum, AA is the usual legal and contract target, and AAA is the highest and rarely required for a whole site. Each level adds success criteria, such as colour contrast at AA.
18

What is compatibility testing?

Testing TypesMedium
Save to ▾
Show answer
Checking the application works across browsers, devices, operating systems, screen sizes and network conditions.
19

What is a test environment?

STLC and Test PlanningEasy
Save to ▾
Show answer
The hardware, software, data and configuration where testing happens, set up to mirror production as closely as practical.
20

What is the difference between path parameters, query parameters and the request body?

Agile, SQL and API TestingEasy
Save to ▾
Show answer
Path parameters identify a specific resource and are part of the URL, as in /users/42. Query parameters filter, sort or paginate and come after a question mark, as in /users?city=Pune&page=2. The request body carries data for creating or updating, usually JSON, in POST, PUT or PATCH. Testers check invalid values in each: a wrong ID in the path, unknown query parameters and missing body fields.
21

What is the difference between retesting and regression testing?

Testing TypesEasy
Save to ▾
Show answer
Retesting, or confirmation testing, checks that a specific bug that was fixed now works, using the same steps as the original bug. Regression testing checks that the fix or a new change has not broken other, previously working features. Retesting is planned for failed cases only, while regression covers a wider set of passing cases. Retesting usually comes first, then regression around the changed area.
22

What is defect leakage?

Bug Life Cycle and JiraMedium
Save to ▾
Show answer
Defects found after release that testing should have caught; leakage % = defects in production / total defects x 100.
23

What are components, labels and fix versions in Jira?

Bug Life Cycle and JiraEasy
Save to ▾
Show answer
Components are fixed sub-parts of a project, such as Payments or Login, often with a default owner. Labels are free-text tags, such as regression or ui, that anyone can add for grouping. Fix version is the release in which the issue is planned to be fixed, while affects version is where the bug was found. Testers use these fields to filter bugs and to build release-wise reports.
24

What is a REST API?

Agile, SQL and API TestingMedium
Save to ▾
Show answer
An API style using HTTP methods on resources identified by URLs, usually exchanging JSON and staying stateless.
25

What is the definition of done?

Agile, SQL and API TestingMedium
Save to ▾
Show answer
A shared checklist for when a story is complete, usually including code review, tests passing, no open critical bugs and documentation updated.
26

What is the difference between a build and a release?

Manual Testing BasicsEasy
Save to ▾
Show answer
A build is a compiled version of the software created from the latest code, often many times a day, and given to QA for testing. A release is a tested, approved version delivered to customers or production, usually with release notes and a version number. Many builds can go through testing before one of them is promoted as a release. Testers always note the build number in bug reports.
27

Why do performance reports use percentiles like p90 and p95 instead of averages?

Performance and Security BasicsMedium
Save to ▾
Show answer
An average hides slow requests. If 90 requests take 1 second and 10 take 10 seconds, the average is 1.9 seconds, which looks fine, but one user in ten waits 10 seconds. The p95 value means 95 percent of requests were faster than it, so it shows what most users actually experience, including the slow tail. Service level targets are usually written as percentiles, such as p95 under 2 seconds.
28

What is a test closure report?

STLC and Test PlanningEasy
Save to ▾
Show answer
A final document summarising what was tested, defects found and open, metrics, lessons learned and the recommendation for release.
29

What is a regression bug and how do you track it in Jira?

Bug Life Cycle and JiraEasy
Save to ▾
Show answer
A regression bug is a feature that worked before but broke after a new change, such as login failing after a profile page update. It is usually treated with higher priority because it affects existing users. In Jira, add a label such as regression, set the affected version and link it to the story or change that caused it. Tracking these labels over time shows where regression coverage is weak.
30

What is the difference between smoke testing in CI and full regression?

Testing TypesMedium
Save to ▾
Show answer
Smoke tests run on every build for quick feedback; full regression runs less often, such as nightly or before release.
31

What does the absence-of-errors fallacy mean?

Manual Testing BasicsMedium
Save to ▾
Show answer
It means that finding and fixing many defects does not guarantee success if the system itself does not meet user needs. A bug-free product built on wrong or misunderstood requirements is still a failure. For example, a perfectly working report that shows the wrong business metric is useless to the client. This is why testers validate against real user expectations, not just the written specification.
32

What are test data and how do you prepare them?

STLC and Test PlanningMedium
Save to ▾
Show answer
The inputs used in tests. Prepare using valid, invalid and boundary values from production-like but masked data, spreadsheets or generators.
33

What is a test case and its components?

Manual Testing BasicsEasy
Save to ▾
Show answer
A set of steps with inputs and expected results. Components: ID, title, preconditions, steps, test data, expected result, actual result and status.
34

What are the typical JIRA workflows for bugs?

Bug Life Cycle and JiraMedium
Save to ▾
Show answer
Statuses like To Do, In Progress, In Review, Ready for QA, Done and Reopened, with transitions that depend on the team's configuration.
35

What is a Three Amigos session?

Agile, SQL and API TestingMedium
Save to ▾
Show answer
Three Amigos is a short meeting where a business person or product owner, a developer and a tester discuss a story before development. The business explains the need, the developer considers how to build it and the tester asks what could go wrong and how it will be verified. The output is clear acceptance criteria and example scenarios. It prevents misunderstandings and reduces bugs found late.
36

Explain the bug life cycle.

Bug Life Cycle and JiraEasy
Save to ▾
Show answer
New → Assigned → Open → Fixed → Retest → Verified → Closed, with Reopened, Rejected, Deferred and Duplicate as side paths.
37

What is regression testing, and when do you automate it?

Testing TypesMedium
Save to ▾
Show answer
Re-testing existing features after a change. Automate stable, repetitive, high-value flows that run every release.
38

What is a sprint retrospective?

Agile, SQL and API TestingMedium
Save to ▾
Show answer
A team meeting at the end of a sprint to discuss what went well, what did not and what to improve next.
39

What is SQL and why do testers use it?

Agile, SQL and API TestingEasy
Save to ▾
Show answer
A language to query databases. Testers use it to verify data saved by the application, prepare test data and check backend results.
40

Verification vs validation?

Manual Testing BasicsEasy
Save to ▾
Show answer
Verification: are we building the product right? (reviews, walkthroughs — no code run). Validation: are we building the right product? (actual testing against user needs).
41

What is the difference between a bug and an enhancement?

Bug Life Cycle and JiraMedium
Save to ▾
Show answer
A bug is behaviour that deviates from agreed requirements; an enhancement is a new or improved capability beyond the current requirements.
42

What are entry and exit criteria?

STLC and Test PlanningMedium
Save to ▾
Show answer
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).
43

What is a test plan and what does it contain?

STLC and Test PlanningEasy
Save to ▾
Show answer
A document defining scope, approach, resources, schedule, entry and exit criteria, risks and deliverables of testing.
44

What is SDLC and STLC?

STLC and Test PlanningEasy
Save to ▾
Show answer
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.
45

What is a locator and what types of locators exist?

Automation Basics for Manual TestersEasy
Save to ▾
Show answer
A locator tells the automation tool how to find an element on the page so it can click, type or check it. Common types are ID, name, CSS selector, XPath, link text, and in modern tools role-based locators such as a button with name Login, plus label, placeholder and test ID locators. A good locator is unique, readable and unlikely to change when the page design changes.
46

What is the V-model?

Manual Testing BasicsMedium
Save to ▾
Show answer
A development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.
47

What is boundary value analysis?

Test Case DesignMedium
Save to ▾
Show answer
Testing at the edges of input ranges, such as 17, 18 and 19 for an age limit of 18, since errors cluster at boundaries.
48

What is the difference between a test suite and a test run?

STLC and Test PlanningMedium
Save to ▾
Show answer
A suite is a collection of related test cases; a run is one execution of a set of tests against a build.
49

What is the difference between alpha and beta testing?

Testing TypesEasy
Save to ▾
Show answer
Alpha is done in-house by internal teams before release; beta is done by a limited group of real users in their own environment.
50

Functional vs non-functional testing?

Testing TypesEasy
Save to ▾
Show answer
Functional testing checks what the system does (login, checkout). Non-functional testing checks how well it does it (performance, security, usability, compatibility).

Frequently asked questions

What happens in the Software Testing rapid-fire round?

Rapid-fire questions are quick definitions and one-line answers that interviewers fire at the start or end of a round to check your Software Testing basics. Aim to answer each in under 20 seconds.

How do I clear the rapid-fire round?

Answer in one or two sentences, then stop. If you don't know, say so quickly and move on; don't guess at length. Revise these the morning of the interview.

Which round comes next?

A typical order is online assessment, telephonic screening, one or two technical rounds, a managerial round and HR. Use the other round pages to practise each stage.

Practise every interview round

Online Assessment questionsTelephonic Interview questionsTechnical Round questionsManagerial Round questionsHR & behavioural questionsFull mock interview

More ways to practise

Company-wise Software Testing questionsPackage-wise Software Testing questionsExperience-wise Software Testing questionsRole-wise Software Testing questionsCity-wise Software Testing questionsMost asked Software Testing questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsSoftware Testing mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsSoftware Testing topic sheets