NEW
Font size
WorksheetsITMC322 QM Prelims Exam
Total questions: 60
Worksheet time: 30mins
A software development team tests an application extensively but still finds defects after release. This demonstrates which principle of testing?
Testing shows the presence of defects
Exhaustive testing is possible
Defect clustering
Testing eliminates all risks
The cost of fixing a defect increases the later it is found in the software development life cycle. Which principle of testing does this relate to?
Pesticide paradox
Early testing
Context-dependent testing
Exhaustive testing is possible
A tester runs the same set of test cases repeatedly and finds no new defects. This is an example of:
Defect clustering
Exhaustive testing
Pesticide paradox
Context-dependent testing
Not all parts of a system contain defects equally. Which principle states that most defects are found in a few modules?
Defect clustering
Early testing
Absence-of-errors fallacy
Testing is context dependent
Testing cannot prove that a system is 100% defect-free, only that defects exist. This is an example of which principle?
Absence-of-errors fallacy
Testing shows the presence of defects
Testing is context-dependent
Early testing
Software developed for an e-commerce site will require different testing than software for a medical device. This is an example of:
Early testing
Context-dependent testing
Defect clustering
Exhaustive testing
A company only involves testers at the end of the development cycle, leading to costly fixes. What principle was violated?
Pesticide paradox
Exhaustive testing
Early testing
Absence-of-errors fallacy
The belief that fixing all defects will result in a perfect system is incorrect. This relates to which principle?
Testing shows the presence of defects
Absence-of-errors fallacy
Pesticide paradox
Defect clustering
What is the main reason exhaustive testing is impossible?
Limited budget
Too many input combinations
Poor software quality
Testers are inexperienced
Risk analysis should be used to prioritize test cases because:
Not all features are equally important
Every function must be tested equally
Testing eliminates all risks
Testing proves software is perfect
The primary reason testing is necessary is because:
It guarantees a defect-free product
Defects are inevitable in software development
Developers always make mistakes
It reduces development costs
Which of the following is NOT a reason why testing is important?
Finding defects
Increasing software complexity
Reducing risk of failure
Building confidence in the system
Which of the following is an example of reducing risk of failure through testing?
Running test cases on critical functionalities before deployment
Fixing defects only after customers report them
Ignoring small issues to save time
Launching the product without testing
A customer reports that the software crashes when performing a transaction. Proper testing would have helped in:
Finding defects
Reducing risk of failure
Building confidence in the system
All of the above
Testing helps in preventing defects by:
Running test cases before coding
Identifying potential issues early in development
Fixing defects after deployment
Ignoring minor issues
A team tests their software rigorously, leading to fewer reported issues post-release. This demonstrates how testing helps in:
Preventing defects
Finding defects
Building confidence in the system
Both a and c
Which testing activity directly contributes to building confidence in the system?
Finding defects and fixing them
Running regression tests before deployment
Ignoring minor bugs in a non-critical system
Releasing software without testing
The earlier testing is performed, the more it contributes to:
Higher development costs
Increasing risk of failure
Preventing defects
Delayed product release
A CEO asks why the company spends money on testing. The best response is:
Testing is just a formality
It helps reduce costs by catching issues early
Developers do not make mistakes
Software is always perfect after coding
A banking application must handle transactions without errors. Which testing benefit is most relevant?
Preventing defects
Reducing risk of failure
Building confidence in the system
All of the above
An incorrect formula was used in a payroll application, leading to wrong salary calculations. This is an example of:
Error
Defect
Failure
Testing issue
A developer misinterprets the requirements and writes incorrect code. This is an example of:
Defect
Error
Failure
Test case mistake
A software module has a known defect but still works correctly in all scenarios. What is missing?
Error
Failure
Risk analysis
Software complexity
A user reports that the application crashes when performing a specific action. This is a:
Defect
Failure
Error
Minor issue
Which of the following can directly cause a failure?
An unhandled exception in the code
Poor UI design
Incorrect requirements
None of the above
A tester notices that requirements are constantly changing, causing defects. This is an example of:
Poor communication
Changing requirements
Time pressures
Software complexity
The biggest contributor to defects in software development is usually:
Programming errors
Human fallibility
Hardware issues
Poor UI design
Rushed software releases often result in more defects. This is due to:
Time pressures
Poor communication
Hardware limitations
Testing errors
A developer was confused by vague requirements and implemented the wrong feature. This is an example of:
Human fallibility
Software complexity
Poor communication
Time pressures
Which of the following factors contributes to software defects?
Changing requirements
Poor communication
Time pressures
All of the above
Which of the following statements best describes software quality?
It is determined by how well the software meets user requirements
It is only measured by the number of defects found
It is defined by how quickly the software is delivered
It depends only on the design of the software
How does testing contribute to software quality?
By reducing defects and ensuring system reliability
By speeding up the development process
By replacing the need for development
By increasing system complexity
What is the ultimate goal of testing in terms of quality?
To find as many defects as possible
To ensure software meets user needs and performs correctly
To make testing faster
To remove all software complexity
A software product meets all technical specifications but fails to satisfy users. What aspect of quality is missing?
Technical correctness
User satisfaction
Security
Performance
Software testing helps ensure:
User requirements are met
Software is free of all defects
No future issues arise
Testing replaces development
This refers to an overarching plan or high-level document that describes testing levels, processes, and strategies within an organization. It ensures testing is structured and standardized.
Test Approach
Test Strategy
Test Policy
Test Process
This consists of the required elements and prerequisites before testing can begin and defines when testing should stop.
Test Approach
Entry and Exit Criteria
Test Basis
Testware
A collection of documents from which system requirements can be inferred; serves as a reference point for designing test cases.
Test Basis
Test Condition
Test Case
Test Strategy
This is a broad term for all artifacts (documents, scripts, data) created during the testing process, including test cases, logs, and reports.
Test Condition
Test Suite
Testware
Test Policy
A structured, ordered set of test cases where the output of one serves as the input for another.
Test Condition
Test Procedure
Test Suite
Test Basis
A document that describes the steps needed to execute a test, including setup, execution, and expected results.
Test Case
Test Procedure
Test Strategy
Test Policy
The act of determining whether the foundation of a system (requirements, documents) can support an effective testing process.
Test Condition
Evaluating Testability
Test Case Design
Test Closure
A specific function, feature, or characteristic that can be verified through one or more test cases.
Test Condition
Test Environment
Test Procedure
Test Strategy
A controlled setting that includes software, hardware, and tools needed to perform testing activities.
Test Basis
Test Environment
Test Suite
Test Policy
A single, detailed set of input values and expected outcomes designed to verify a specific system function.
Test Procedure
Test Case
Test Condition
Test Strategy
This step involves defining test objectives, identifying risks, and setting up schedules and required resources.
Test Implementation and Execution
Test Planning
Test Closure
Test Analysis
Monitoring test progress, tracking deviations, and taking corrective actions fall under which process?
Test Control
Test Execution
Test Closure
Test Planning
Reviewing system documentation and identifying potential test conditions occur in which phase?
Test Closure
Test Analysis and Design
Test Planning
Test Execution
Writing test cases, preparing test data, and setting up the test environment are activities within:
Test Planning
Test Implementation
Test Execution
Evaluating Exit Criteria
Running test cases, logging results, and reporting discrepancies occur during:
Test Execution
Test Planning
Test Control
Test Closure
After executing test cases, stakeholders need to decide whether more testing is required. This is part of:
Evaluating Exit Criteria and Reporting
Test Implementation
Test Closure
Test Analysis
This phase ensures all planned test deliverables have been completed and archived for future use.
Test Control
Test Closure Activities
Test Implementation
Evaluating Exit Criteria
Identifying test conditions and designing appropriate test cases occurs in:
Test Analysis and Design
Test Closure
Test Execution
Test Control
Which phase involves verifying if test environment setup is correct before actual testing begins?
Test Analysis
Test Execution
Test Planning
Test Implementation
Before the final product release, checking whether testing met pre-defined success criteria happens in:
Test Analysis
Test Closure
Evaluating Exit Criteria
Test Planning
When testers create a structured collection of test cases that are dependent on one another, they are performing:
Test Implementation
Test Suite Development
Test Closure
Test Strategy Design
Corrective actions for unexpected results during testing are taken in:
Test Execution
Test Control
Test Closure
Test Planning
Writing detailed logs of test activities to ensure traceability and accountability is part of:
Test Closure
Test Control
Test Execution
Evaluating Exit Criteria
Creating a report summarizing the results of testing efforts for stakeholders happens during:
Test Execution
Test Planning
Evaluating Exit Criteria and Reporting
Test Closure
Ensuring that lessons learned from testing are documented for future projects is part of:
Evaluating Exit Criteria
Test Closure
Test Planning
Test Execution
