Software Testing Last-Minute Revision
Quickly revise the questions you picked. Add questions from the interview-questions lists with Save to → Last-Minute Revision.
30 quick revision notes for Software Testing
- Verification asks are we building the product right through reviews; validation asks are we building the right product through actual testing.
- Quality assurance prevents defects by improving processes, while quality control detects defects by checking the actual product.
- An error is a human mistake, a defect is the flaw in the code, and a failure is the wrong behaviour seen when it runs.
- The seven testing principles include: testing shows presence of defects, exhaustive testing is impossible, and early testing saves time and money.
- Smoke testing checks if a build is stable enough to test; sanity testing checks a specific fix or change works.
- Retesting confirms a fixed bug now works; regression testing confirms the change did not break existing features.
- Equivalence partitioning divides inputs into groups that behave the same, so one value from each group is tested.
- Boundary value analysis tests values at and just around the edges, such as 17, 18, 60 and 61 for an 18 to 60 range.
- Decision tables cover combinations of conditions and their actions; state transition testing covers valid and invalid state changes.
- A test scenario says what to test at a high level; a test case gives steps, data and expected results for how to test it.
- Severity is the technical impact of a bug on the system; priority is how urgently the business wants it fixed.
- A good bug report has a clear title, environment and build, exact steps, expected and actual results, and evidence.
- Typical bug states are New, Assigned, Open, Fixed, Retest, Verified, Closed, plus Reopened, Deferred, Rejected and Duplicate.
- Defect leakage is the share of defects found after release; defect removal efficiency is the share found before release.
- STLC phases are requirement analysis, test planning, test case design, environment setup, test execution and test closure.
- Entry criteria say when testing can start; exit criteria say when testing can be considered complete for a release.
- A requirement traceability matrix maps requirements to test cases and defects to prove every requirement is covered.
- A test strategy is a long-term, high-level approach; a test plan applies it to one project or release with scope and schedule.
- In Scrum, testers join sprint planning, daily stand-up, refinement, sprint review and retrospective, and help define done.
- Acceptance criteria are the testable conditions a user story must meet, often written in Given, When, Then format.
- INNER JOIN returns matching rows only; LEFT JOIN returns all rows from the left table, with nulls where no match exists.
- WHERE filters rows before grouping, HAVING filters groups after GROUP BY, which is useful to find duplicates with COUNT greater than 1.
- GET reads data, POST creates, PUT replaces, PATCH partially updates and DELETE removes a resource in a REST API.
- Status code 200 means OK, 201 created, 400 bad request, 401 not authenticated, 403 forbidden, 404 not found, 500 server error.
- Mobile testing must cover real devices, OS versions, screen sizes, interrupts, permissions, network changes and install or update flows.
- Load testing checks expected traffic, stress testing goes beyond limits, spike testing checks sudden jumps and soak testing checks long durations.
- Use percentiles like p95 for response time because averages hide slow requests that many users actually experience.
- Authentication verifies identity; authorization decides what an authenticated user is allowed to access or change.
- SQL injection and XSS come from untrusted input; test by entering special characters and scripts, and confirm the server validates and encodes.
- UAT is done by business users to confirm the system meets real needs, and it happens after system testing and before go-live.
Night-before checklist
- Revise your saved questions on this page once, aloud.
- Read the quick notes and mark any you cannot explain in one line.
- Rehearse a two-minute self-introduction and two project stories.
- Keep CV, ID, laptop charger and interview link ready; sleep on time.
Frequently asked questions
How does Last-Minute Revision work?
On any question page, open Save to → Last-Minute Revision. Saved questions appear here with their answers, so the night before an interview you revise only what you found hard.
Is my list saved?
Yes, in this browser. Guests can save 5 questions; free accounts can save 20 for revision and 100 for the 7-day plan.
What should I revise last before a Software Testing interview?
Your saved misses first, then the quick notes on this page, then one or two project stories. Avoid learning brand-new topics the night before.
Find questions to save
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