Unlock hundreds more features
Save your Quiz to the Dashboard
View and Export Results
Use AI to Create Quizzes and Analyse Results

OR
Sign inSign in with Facebook
Sign inSign in with Google
Quizzes > Programming & Software

Manual software testing online test: check your QA skills

Quick, free manual testing quiz. Instant results.

Editorial: Review CompletedCreated By: Martin Neal-PriceUpdated Aug 24, 2025
Difficulty: Moderate
2-5mins
Learning OutcomesCheat Sheet
Paper art illustration of software testing quiz on sky blue background with test doc, magnifier, check marks

This manual software testing quiz helps you check core QA skills: finding bugs, writing clear test cases, and choosing the right approach. See your strengths, spot gaps for interviews, and keep learning with the jQuery quiz, the operating systems test, and the quality management quiz today.

What is the primary purpose of manual software testing?
To monitor production servers
To automate test scripts
To write code for the application
To manually execute test cases and identify defects
Manual testing involves executing test cases by human testers without automation tools to find defects, ensuring the product meets requirements. It is essential for exploratory testing, usability checks, and ad-hoc scenarios. It helps identify issues that automated tests may miss.
What is a test case?
An error in software functionality
The final report after testing completion
A document describing test objective, steps, input, expected result
A piece of code that executes tests automatically
A test case is a set of conditions, steps, inputs, and expected results developed to verify a particular aspect of a software application. It guides testers through a sequence of actions to validate functionality. Detailed test cases improve reproducibility and traceability.
What is a defect in software testing?
A short-term workaround
Any variance between expected and actual results
A plan for testing activities
An automated test script
A defect (or bug) is any flaw or discrepancy where the software does not behave as intended according to requirements or specifications. Defects can be functional, performance-related, or usability-focused. Identifying and reporting defects is a core task in testing.
Which document outlines the scope, objectives, resources, and schedule of testing activities?
Test Case
Defect Report
Test Summary Report
Test Plan
A Test Plan is a formal document that defines the scope, approach, resources, schedule, and focus of testing activities. It serves as a blueprint for the entire testing process and includes risk analysis and entry/exit criteria. Stakeholders review and approve the Test Plan before execution begins.
What is regression testing?
Testing only the user interface
Testing the first build of an application
Testing without any test cases
Testing after changes to ensure no new defects
Regression testing is the process of re-running previously executed test cases after modifications to ensure that existing functionality has not been adversely affected. It is critical in agile environments where frequent changes are made. Automated regression suites are often employed for efficiency.
Which technique divides input data into valid and invalid classes?
Decision table testing
Equivalence partitioning
State transition testing
Boundary value analysis
Equivalence partitioning groups input data into partitions where test cases in one partition are assumed to be treated the same by the system. It reduces the number of test cases by selecting representative values from each partition. Both valid and invalid partitions are considered.
What does boundary value analysis focus on?
Generating random test data
Mapping causes to effects
Testing values at the edges of input domains
Partitioning input data into classes
Boundary value analysis tests inputs at their edge values (minimum, maximum, just inside/outside boundaries) because errors often occur at the boundaries of input domains. It complements equivalence partitioning by focusing on edge cases. It helps detect off-by-one and range-checking errors.
What is smoke testing?
A quick check to ensure basic functionality works
Performance testing under high load
Testing with no documentation
A comprehensive testing of all features
Smoke testing is a preliminary test to reveal simple failures severe enough to reject a prospective software release. It checks core functionalities without going into deeper levels of testing. It is often called 'build verification testing.'
What is the main difference between smoke testing and sanity testing?
Smoke testing is shallow and wide; sanity is narrow and deep
Smoke is narrow and deep; sanity is shallow and wide
Both are identical terms
Both focus on performance
Smoke testing covers a broad set of basic tests to ensure the stability of a build, while sanity testing focuses on a specific functionality or bug fix. Smoke is performed first, then sanity checks deeper areas after minor changes. Both are types of acceptance testing.
Which level of testing focuses on the interaction between integrated modules?
System Testing
Acceptance Testing
Unit Testing
Integration Testing
Integration testing verifies the interfaces and interaction between integrated modules, ensuring they work together as expected. It can be carried out using top-down, bottom-up, or hybrid approaches. It follows unit testing and precedes system testing.
What is a test scenario?
A log of defects found in testing
A summary report of testing metrics
A high-level condition for test coverage
A detailed test script with steps
A test scenario describes a functionality or feature that needs to be tested, providing a high-level view of what to test. Scenarios help ensure comprehensive coverage of requirements without detailing every step. They are useful for exploratory testing and planning.
What is negative testing?
Testing that always fails
Testing with invalid inputs to check error handling
Testing only the positive flow without errors
Testing performance under negative load
Negative testing involves supplying invalid or unexpected inputs to ensure the application handles them gracefully, without crashing. It verifies robustness and error messages. It is crucial for uncovering edge-case failures.
Which document specifies the criteria for closing the testing activities?
Traceability Matrix
Test Case
Test Plan
Test Closure Report
The Test Closure Report summarizes testing activities and defines exit criteria, including completion of test cases, defect status, and coverage metrics. It provides lessons learned and recommendations for future cycles. It formally closes the testing phase.
What does test coverage measure?
The time taken to execute all tests
The number of defects found per hour
The percentage of code executed by tests
The count of test environments
Test coverage quantifies the extent to which source code, requirements, or functionality has been exercised by tests. It can refer to code coverage, requirement coverage, or test case coverage. High coverage reduces risk of undiscovered defects.
In a defect management context, what is the difference between severity and priority?
Both terms are interchangeable
Severity is fix order; priority is impact
Severity is impact; priority is fix order
Neither is used in defect tracking
Severity indicates the impact of a defect on the application's functionality, while priority defines the order in which defects should be fixed. A defect can be high severity but low priority if it rarely occurs. Proper classification helps manage resources.
What is decision table testing used for?
Prioritizing test cases based on risk
Randomly generating test data
Comparing expected vs actual results after testing
Mapping business rules with combinations of inputs and outputs
Decision table testing is a black-box technique that uses a tabular representation of inputs, conditions, and resulting actions to derive test cases. It ensures coverage of all logical combinations of conditions. It is especially useful for complex business rules.
Which testing technique uses logical relationships between causes and effects?
Boundary value analysis
Equivalence partitioning
State transition testing
Cause-effect graphing
Cause-effect graphing models input conditions (causes) and output effects using boolean logic to derive test cases. It translates the graph into a decision table to cover complex condition combinations. This technique improves coverage of conditional logic.
What characterizes exploratory testing?
Strict adherence to predefined test cases
Regression testing after fixes
Automated script generation for each requirement
Simultaneous learning, test design, and execution without scripts
Exploratory testing is an unscripted approach where testers actively learn the application, design tests on the fly, and execute them simultaneously. It leverages tester creativity and domain knowledge. It is effective for finding critical issues quickly.
How is defect density calculated?
Total test cases divided by defects found
Number of defects found divided by size of code (e.g., lines of code)
Number of testers divided by defects found
Runtime divided by defects found
Defect density is a quality metric calculated by dividing the number of defects identified by the size of the software component, often measured in lines of code or function points. It helps teams assess code quality and identify high-risk modules. Lower defect density indicates better code quality.
What is pairwise testing often used for?
Executing tests in pairs of testers
Validating user interface controls in pairs
Testing two modules at a time in integration testing
Reducing test combinations by covering all pairs of input parameters
Pairwise testing, or all-pairs testing, selects test cases to cover every possible pair of input parameter values. It significantly reduces the total number of combinations while maintaining defect detection effectiveness. It is useful when there are many parameters.
Which of the following is a typical stage in the defect life cycle after 'Retest'?
Reopen (if still not fixed) or Closed (if fix is successful)
Deferred (always)
Duplicate
Reassign to developer
After a developer fixes a defect and it is retested, the defect is either marked 'Closed' if the fix is verified or 'Reopened' if the issue persists. Other statuses like 'Deferred' or 'Duplicate' apply in different contexts. The defect life cycle ensures clear tracking.
What is risk-based testing?
Running tests in a production environment
Prioritizing tests based on potential impact and likelihood of failure
Testing only risky parts of code with no documentation
Automating tests for high-risk modules exclusively
Risk-based testing focuses on identifying, assessing, and prioritizing tests according to the potential business impact and likelihood of failures. It helps allocate limited resources to the most critical areas. It aligns test efforts with organizational risk tolerance.
What does TMMi stand for in software testing maturity models?
Test Metric Maturity Increment
Test Maturity Model Integration
Technical Maturity Model Index
Test Management Model Increment
TMMi stands for Test Maturity Model Integration, a framework for assessing and improving testing processes within an organization. It provides maturity levels from initial to optimized. It helps teams benchmark and enhance their test capabilities.
What is model-based testing?
Running tests only in production models
Manual testing of UML diagrams
Scripting tests based on model code modules
Generating test cases from abstract representations of system behavior
Model-based testing uses formal or semi-formal models of system behavior (like state machines or diagrams) to automatically generate test cases. It ensures consistency between requirements and tests. It can increase coverage and reduce manual effort.
In the SFDIPOT heuristic for test strategy, what does the 'P' stand for?
Process
Parameter
Platform
Performance
SFDIPOT is a mnemonic heuristic for test coverage: Structure, Function, Data, Interfaces, Platform, Operations, Time. 'P' stands for Platform, focusing on different OS, browsers, or hardware environments. It guides test strategy development.
0
{"name":"What is the primary purpose of manual software testing?", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"What is the primary purpose of manual software testing?, What is a test case?, What is a defect in software testing?","img":"https://www.quiz-maker.com/3012/images/ogquiz.png"}

Study Outcomes

  1. Understand Manual Testing Fundamentals -

    Grasp core principles of manual software testing through targeted questions, ensuring you can articulate testing concepts with confidence.

  2. Apply Real-World QA Scenarios -

    Use insights from practical manual QA interview questions to simulate bug hunts and learn effective test case execution techniques.

  3. Analyze Test Case Design -

    Evaluate test case structures and best practices in our manual testing practice test to identify gaps and optimize coverage.

  4. Evaluate Defect Reporting Skills -

    Refine your ability to document and report bugs clearly, following industry standards highlighted in this free QA testing quiz.

  5. Navigate Online Quiz Formats -

    Familiarize yourself with the software testing quiz online interface, boosting efficiency and reducing test-taking anxiety.

  6. Boost QA Interview Readiness -

    Measure your proficiency against real interview questions and strengthen areas of weakness for upcoming manual QA interviews.

Cheat Sheet

  1. Boundary Value Analysis & Equivalence Partitioning -

    Boundary Value Analysis (BVA) and Equivalence Partitioning (EP) help you cover edge cases effectively by testing inputs at extremes and representative classes. For example, if valid ages are 18 - 60, test 17, 18, 60 and 61 to catch off-by-one errors (University of Maryland). Remember the mnemonic "BEE" (Boundary, Equivalence, Extremes) to recall these key black-box techniques (ISTQB, 2023).

  2. Defect Life Cycle & Prioritization -

    According to IEEE 829, tracking defects from "New" through "Verified" to "Closed" ensures clear accountability and timely fixes. Use a 2×2 matrix combining Severity (impact) and Priority (urgency) to classify bugs - High/High issues get top focus. A quick "SP" mnemonic (Severity before Priority) helps you articulate this in your manual QA interview questions.

  3. Exploratory Testing Techniques -

    Exploratory testing is unscripted, relying on tester skills and intuition to uncover hidden issues (Cem Kaner, 2006). Charter-driven sessions with timeboxes (e.g., 90-minute tours) and mind maps help structure your approach while remaining adaptive. Many testers swear by the acronym "SCAn" (Session, Charter, Analyze, note) for session-based test management (University of Texas).

  4. Test Documentation & Traceability -

    Clear artifacts - Test Plan, Test Strategy and Requirement Traceability Matrix (RTM) - align your testing scope with business needs (ISTQB Foundation). The RTM maps each requirement ID to its test cases, ensuring 100% coverage and easy audit trails. Think "Plan, Map, Validate" to remember your documentation workflow.

  5. Practice Tests & Interview Prep -

    Sharpen your skills with a manual software testing quiz or software testing quiz online and review common pitfalls in a free QA testing quiz. Simulate real interview scenarios by framing answers using the STAR method (Situation, Task, Action, Result) when tackling manual testing practice test questions. Consistent practice on manual QA interview questions boosts confidence and performance!

Make a Quiz (FREE) Copy & Edit This Quiz Create a Quiz with AI

Programming & Software Quizzes

Powered by: Quiz Maker