Basic Manual Testing questions
1. What is the difference between verification and validation?
Verification checks we are building the product right: reviews, walkthroughs and inspections of documents and code without running it. Validation checks we built the right product by executing the software against user requirements.
2. What is STLC?
The Software Testing Life Cycle: requirement analysis, test planning, test case design, test environment setup, test execution and test closure, each with entry and exit criteria.
3. Severity vs priority?
Severity is the impact of a defect on the system (set by testers). Priority is how soon it must be fixed (set by the business). A spelling mistake in the company name on the home page is low severity but high priority.
4. Smoke vs sanity testing?
Smoke testing is a broad, shallow check that a new build is stable enough for further testing. Sanity testing is a narrow, focused check that a specific fix or feature works after a change.
Intermediate Manual Testing questions
5. Explain the bug life cycle.
New, then Assigned, Open, Fixed, Retest, and finally Verified and Closed. A bug can also be Rejected, Deferred, marked Duplicate, or Reopened if retesting fails.
6. What is regression testing?
Re-running existing tests after code changes to make sure working features did not break. Because it repeats every release, regression suites are the first candidates for automation.
7. Explain boundary value analysis and equivalence partitioning.
Equivalence partitioning divides inputs into groups that should behave the same and tests one value from each. Boundary value analysis tests at and just around the edges. For an age field of 18 to 60, test 17, 18, 60 and 61.
8. What makes a good test case?
A clear ID and title, preconditions, test data, numbered steps, an expected result, and traceability to a requirement. It should be independent, repeatable and test one thing.
Advanced Manual Testing questions
9. What is a Requirement Traceability Matrix?
An RTM maps each requirement to its test cases and defects. It proves coverage, shows which requirements are untested and helps assess the impact of requirement changes.
10. How does testing work in Agile?
Testers join sprint planning, refine acceptance criteria, test stories inside the same sprint, automate regression continuously and take part in daily stand-ups and retrospectives. Quality is a shared team responsibility rather than a final phase.
Want to practise these with a trainer? APEX live batches include mock interviews, real projects and placement support. See upcoming batches.