Manual Testing Methodologies Questions

Core manual testing concepts and approaches for functional quality assurance and user experience validation. Candidates should understand testing types such as functional testing, regression testing, boundary and edge case testing, exploratory testing, scripted testing, ad hoc testing, positive and negative test design, and acceptance testing. Know the differences between black box testing, white box testing awareness, and grey box testing, and be able to select appropriate manual testing approaches for a given feature or release, design test cases and test charters, and explain when manual testing is preferred over automation.

EasyTechnical

56 practiced

Compare and contrast black box, white box, and grey box testing specifically from a manual QA perspective. For each approach define it, list typical manual techniques you would use, state when it is preferred, and give one example manual test for a login API illustrating that approach.

EasyTechnical

91 practiced

Describe exploratory testing: what it is, how it differs from scripted/manual test execution, when it is most valuable, how to document findings during a session, and provide one useful exploratory heuristic you might use for a new feature.

MediumTechnical

66 practiced

With 48 hours until release and a backlog of 50 manual test cases with varying priority, complexity, and risk, describe a concrete prioritization and execution approach. Include criteria to select which tests to run first, gating tests to verify before deployment, and how you'll communicate status and residual risk to stakeholders.

MediumTechnical

51 practiced

Explain how session-based exploratory testing (SBTM) works and propose a set of metrics, artifacts, and reporting practices to measure and communicate coverage and outcomes from manual SBTM sessions to stakeholders.

Sample Answer

**Overview of SBTM (how it works)** Session-Based Test Management organizes exploratory testing into time-boxed sessions (typically 60–120 mins) with a clear charter (goal), tester, mission, and heuristics. Testers explore, design, and execute simultaneously, logging actions, observations, and bugs. After each session, a debrief (peer or manager) evaluates findings and next charters.

**Practical workflow** - Define charters from risks/user journeys. - Schedule sessions and assign testers. - Use a session sheet to log start/end time, scope, tools, notes, bugs, and coverage artifacts (screenshots, logs, steps). - Debrief within 24 hours to convert notes to formal bugs/actions.

**Metrics to measure & why** - Sessions completed vs planned (progress) - Time per session & tester utilization (efficiency) - Bug yield per session and severity distribution (effectiveness) - Coverage map: charters exercised vs total risk areas (coverage) - Exploration depth: unique test ideas / session or new coverage items found (thoroughness) - Reproducibility rate of issues reported (quality of reporting)

**Artifacts to produce** - Session sheet (charter, timeline, notes, risks, test data used) - Session log/export (actions, commands, screenshots, network/log captures) - Bug reports with session ID and repro steps excerpt - Coverage matrix mapping charters to features/requirements

**Reporting practices to stakeholders** - Weekly dashboard: sessions planned/done, top defects by severity, coverage heatmap. - Attach representative session sheets to high-impact bugs. - Trend reports: bug yield per session over time, time-to-detect defects. - Short debrief summaries for releases: what was explored, remaining risk areas, recommended next charters.

**Example session sheet fields** - Session ID, charter, tester, start/end, tools, steps/highlights, bugs raised (IDs), artifacts links, confidence rating, follow-ups.

This approach gives stakeholders concise quantitative progress (metrics) plus qualitative evidence (session sheets, artifacts) so they can trust exploratory outcomes and residual risk assessments.

EasyTechnical

55 practiced

Explain manual regression testing: its goals, when to run it, and how you would plan a manual regression cycle for a minor release that contains bug fixes and small UI changes. Include criteria for selecting which manual test cases to run.

Unlock Full Question Bank

Get access to hundreds of Manual Testing Methodologies interview questions and detailed answers.

Join thousands of developers preparing for their dream job.