wayground logo

Free Printable Worksheets

NEW

Font size

S
M
L
XL
Worksheets

ITMC322 QM Prelims Exam

Total questions: 60

Worksheet time: 30mins

Name
Class
Date
1.

A software development team tests an application extensively but still finds defects after release. This demonstrates which principle of testing?

a)

Testing shows the presence of defects

b)

Exhaustive testing is possible

c)

Defect clustering

d)

Testing eliminates all risks

2.

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?

a)

Pesticide paradox

b)

Early testing

c)

Context-dependent testing

d)

Exhaustive testing is possible

3.

A tester runs the same set of test cases repeatedly and finds no new defects. This is an example of:

a)

Defect clustering

b)

Exhaustive testing

c)

Pesticide paradox

d)

Context-dependent testing

4.

Not all parts of a system contain defects equally. Which principle states that most defects are found in a few modules?

a)

Defect clustering

b)

Early testing

c)

Absence-of-errors fallacy

d)

Testing is context dependent

5.

Testing cannot prove that a system is 100% defect-free, only that defects exist. This is an example of which principle?

a)

Absence-of-errors fallacy

b)

Testing shows the presence of defects

c)

Testing is context-dependent

d)

Early testing

6.

Software developed for an e-commerce site will require different testing than software for a medical device. This is an example of:

a)

Early testing

b)

Context-dependent testing

c)

Defect clustering

d)

Exhaustive testing

7.

A company only involves testers at the end of the development cycle, leading to costly fixes. What principle was violated?

a)

Pesticide paradox

b)

Exhaustive testing

c)

Early testing

d)

Absence-of-errors fallacy

8.

The belief that fixing all defects will result in a perfect system is incorrect. This relates to which principle?

a)

Testing shows the presence of defects

b)

Absence-of-errors fallacy

c)

Pesticide paradox

d)

Defect clustering

9.

What is the main reason exhaustive testing is impossible?

a)

Limited budget

b)

Too many input combinations

c)

Poor software quality

d)

Testers are inexperienced

10.

Risk analysis should be used to prioritize test cases because:

a)

Not all features are equally important

b)

Every function must be tested equally

c)

Testing eliminates all risks

d)

Testing proves software is perfect

11.

The primary reason testing is necessary is because:

a)

It guarantees a defect-free product

b)

Defects are inevitable in software development

c)

Developers always make mistakes

d)

It reduces development costs

12.

Which of the following is NOT a reason why testing is important?

a)

Finding defects

b)

Increasing software complexity

c)

Reducing risk of failure

d)

Building confidence in the system

13.

Which of the following is an example of reducing risk of failure through testing?

a)

Running test cases on critical functionalities before deployment

b)

Fixing defects only after customers report them

c)

Ignoring small issues to save time

d)

Launching the product without testing

14.

A customer reports that the software crashes when performing a transaction. Proper testing would have helped in:

a)

Finding defects

b)

Reducing risk of failure

c)

Building confidence in the system

d)

All of the above

15.

Testing helps in preventing defects by:

a)

Running test cases before coding

b)

Identifying potential issues early in development

c)

Fixing defects after deployment

d)

Ignoring minor issues

16.

A team tests their software rigorously, leading to fewer reported issues post-release. This demonstrates how testing helps in:

a)

Preventing defects

b)

Finding defects

c)

Building confidence in the system

d)

Both a and c

17.

Which testing activity directly contributes to building confidence in the system?

a)

Finding defects and fixing them

b)

Running regression tests before deployment

c)

Ignoring minor bugs in a non-critical system

d)

Releasing software without testing

18.

The earlier testing is performed, the more it contributes to:

a)

Higher development costs

b)

Increasing risk of failure

c)

Preventing defects

d)

Delayed product release

19.

A CEO asks why the company spends money on testing. The best response is:

a)

Testing is just a formality

b)

It helps reduce costs by catching issues early

c)

Developers do not make mistakes

d)

Software is always perfect after coding

20.

A banking application must handle transactions without errors. Which testing benefit is most relevant?

a)

Preventing defects

b)

Reducing risk of failure

c)

Building confidence in the system

d)

All of the above

21.

An incorrect formula was used in a payroll application, leading to wrong salary calculations. This is an example of:

a)

Error

b)

Defect

c)

Failure

d)

Testing issue

22.

A developer misinterprets the requirements and writes incorrect code. This is an example of:

a)

Defect

b)

Error

c)

Failure

d)

Test case mistake

23.

A software module has a known defect but still works correctly in all scenarios. What is missing?

a)

Error

b)

Failure

c)

Risk analysis

d)

Software complexity

24.

A user reports that the application crashes when performing a specific action. This is a:

a)

Defect

b)

Failure

c)

Error

d)

Minor issue

25.

Which of the following can directly cause a failure?

a)

An unhandled exception in the code

b)

Poor UI design

c)

Incorrect requirements

d)

None of the above

26.

A tester notices that requirements are constantly changing, causing defects. This is an example of:

a)

Poor communication

b)

Changing requirements

c)

Time pressures

d)

Software complexity

27.

The biggest contributor to defects in software development is usually:

a)

Programming errors

b)

Human fallibility

c)

Hardware issues

d)

Poor UI design

28.

Rushed software releases often result in more defects. This is due to:

a)

Time pressures

b)

Poor communication

c)

Hardware limitations

d)

Testing errors

29.

A developer was confused by vague requirements and implemented the wrong feature. This is an example of:

a)

Human fallibility

b)

Software complexity

c)

Poor communication

d)

Time pressures

30.

Which of the following factors contributes to software defects?

a)

Changing requirements

b)

Poor communication

c)

Time pressures

d)

All of the above

31.

Which of the following statements best describes software quality?

a)

It is determined by how well the software meets user requirements

b)

It is only measured by the number of defects found

c)

It is defined by how quickly the software is delivered

d)

It depends only on the design of the software

32.

How does testing contribute to software quality?

a)

By reducing defects and ensuring system reliability

b)

By speeding up the development process

c)

By replacing the need for development

d)

By increasing system complexity

33.

What is the ultimate goal of testing in terms of quality?

a)

To find as many defects as possible

b)

To ensure software meets user needs and performs correctly

c)

To make testing faster

d)

To remove all software complexity

34.

A software product meets all technical specifications but fails to satisfy users. What aspect of quality is missing?

a)

Technical correctness

b)

User satisfaction

c)

Security

d)

Performance

35.

Software testing helps ensure:

a)

User requirements are met

b)

Software is free of all defects

c)

No future issues arise

d)

Testing replaces development

36.

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.

a)

Test Approach

b)

Test Strategy

c)

Test Policy

d)

Test Process

37.

This consists of the required elements and prerequisites before testing can begin and defines when testing should stop.

a)

Test Approach

b)

Entry and Exit Criteria

c)

Test Basis

d)

Testware

38.

A collection of documents from which system requirements can be inferred; serves as a reference point for designing test cases.

a)

Test Basis

b)

Test Condition

c)

Test Case

d)

Test Strategy

39.

This is a broad term for all artifacts (documents, scripts, data) created during the testing process, including test cases, logs, and reports.

a)

Test Condition

b)

Test Suite

c)

Testware

d)

Test Policy

40.

A structured, ordered set of test cases where the output of one serves as the input for another.

a)

Test Condition

b)

Test Procedure

c)

Test Suite

d)

Test Basis

41.

A document that describes the steps needed to execute a test, including setup, execution, and expected results.

a)

Test Case

b)

Test Procedure

c)

Test Strategy

d)

Test Policy

42.

The act of determining whether the foundation of a system (requirements, documents) can support an effective testing process.

a)

Test Condition

b)

Evaluating Testability

c)

Test Case Design

d)

Test Closure

43.

A specific function, feature, or characteristic that can be verified through one or more test cases.

a)

Test Condition

b)

Test Environment

c)

Test Procedure

d)

Test Strategy

44.

A controlled setting that includes software, hardware, and tools needed to perform testing activities.

a)

Test Basis

b)

Test Environment

c)

Test Suite

d)

Test Policy

45.

A single, detailed set of input values and expected outcomes designed to verify a specific system function.

a)

Test Procedure

b)

Test Case

c)

Test Condition

d)

Test Strategy

46.

This step involves defining test objectives, identifying risks, and setting up schedules and required resources.

a)

Test Implementation and Execution

b)

Test Planning

c)

Test Closure

d)

Test Analysis

47.

Monitoring test progress, tracking deviations, and taking corrective actions fall under which process?

a)

Test Control

b)

Test Execution

c)

Test Closure

d)

Test Planning

48.

Reviewing system documentation and identifying potential test conditions occur in which phase?

a)

Test Closure

b)

Test Analysis and Design

c)

Test Planning

d)

Test Execution

49.

Writing test cases, preparing test data, and setting up the test environment are activities within:

a)

Test Planning

b)

Test Implementation

c)

Test Execution

d)

Evaluating Exit Criteria

50.

Running test cases, logging results, and reporting discrepancies occur during:

a)

Test Execution

b)

Test Planning

c)

Test Control

d)

Test Closure

51.

After executing test cases, stakeholders need to decide whether more testing is required. This is part of:

a)

Evaluating Exit Criteria and Reporting

b)

Test Implementation

c)

Test Closure

d)

Test Analysis

52.

This phase ensures all planned test deliverables have been completed and archived for future use.

a)

Test Control

b)

Test Closure Activities

c)

Test Implementation

d)

Evaluating Exit Criteria

53.

Identifying test conditions and designing appropriate test cases occurs in:

a)

Test Analysis and Design

b)

Test Closure

c)

Test Execution

d)

Test Control

54.

Which phase involves verifying if test environment setup is correct before actual testing begins?

a)

Test Analysis

b)

Test Execution

c)

Test Planning

d)

Test Implementation

55.

Before the final product release, checking whether testing met pre-defined success criteria happens in:

a)

Test Analysis

b)

Test Closure

c)

Evaluating Exit Criteria

d)

Test Planning

56.

When testers create a structured collection of test cases that are dependent on one another, they are performing:

a)

Test Implementation

b)

Test Suite Development

c)

Test Closure

d)

Test Strategy Design

57.

Corrective actions for unexpected results during testing are taken in:

a)

Test Execution

b)

Test Control

c)

Test Closure

d)

Test Planning

58.

Writing detailed logs of test activities to ensure traceability and accountability is part of:

a)

Test Closure

b)

Test Control

c)

Test Execution

d)

Evaluating Exit Criteria

59.

Creating a report summarizing the results of testing efforts for stakeholders happens during:

a)

Test Execution

b)

Test Planning

c)

Evaluating Exit Criteria and Reporting

d)

Test Closure

60.

Ensuring that lessons learned from testing are documented for future projects is part of:

a)

Evaluating Exit Criteria

b)

Test Closure

c)

Test Planning

d)

Test Execution