1.1 What is Testing?

Question 1

List the 9 Testing Objectives. Include the Mnemonic and full Objectives

Answer 1

ETERVVPBV = e(a)ter very very peanut butter vanilla
- Evaluating work products
- Triggering failures
- Ensuring coverage
- Reducing Risk
- Verifying Reqs Fulfilled
- Verifying Compliance
- Providing stakeholders info
- Building confidence in quality
- Validating completeness

Question 2

What’s the first test objective in ETERVVPBV?

Answer 2

Evaluating work products (like requirements, user stories, designs, and code)

Question 3

What’s the second test objective in ETERVVPBV?

Answer 3

Triggering failures (and finding defects)

Question 4

What’s the third test objective in ETERVVPBV?

Answer 4

Ensuring coverage (of the test object as required)

Question 5

What’s the fourth test objective in ETERVVPBV?

Answer 5

Reducing risk (of inadequate software quality)

Question 6

What’s the fifth test objective in ETERVVPBV?

Answer 6

Verifying requirements are fulfilled (as specified)

Question 7

What’s the sixth test objective in ETERVVPBV?

Answer 7

Verifying compliance (with contractual, legal, and regulatory requirements)

Question 8

What’s the seventh test objective in ETERVVPBV?

Answer 8

Providing info to stakeholders (to help them make informed decisions)

Question 9

What’s the eighth test objective in ETERVVPBV?

Answer 9

Building confidence (the quality of the test object)

Question 10

What’s the ninth test objective in ETERVVPBV?

Answer 10

Validating completeness (and that the test object works as expected)

Question 11

What are 5 reasons test objectives may vary? (PTRS Business)

Answer 11

• product
• test level
• risks
• SDLC being followed
• business context

Question 12

What’s the difference between testing and debugging?

Answer 12

Testing is concerned with triggering failures and finding defects.

Debugging is concerning with reproducing errors, root cause analysis, and fixing defects.

Question 13

What’s the difference between dynamic testing and static testing?

Answer 13

Dynamic testing triggers failures caused by defects by actually running the software. Error reproduction and confirmation or regression testing is required to resolve these issues.

Static testing finds defects directly by analyzing code and does not trigger failures. No confirmation or regression testing is needed because these errors can be directly resolved.