Test plan structure in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a test plan?

A test plan is a detailed document that describes the strategy, scope, resources, and schedule of testing activities. It guides the testing process to ensure quality.

beginner

Name three main sections of a test plan.

Common sections include: 1) Test Plan Identifier, 2) Test Items, 3) Test Strategy, 4) Test Schedule, 5) Resources, 6) Risks and Contingencies.

beginner

What information does the 'Test Items' section contain?

It lists the features or components of the software that will be tested, including versions and any related documentation.

intermediate

Why is the 'Test Strategy' section important in a test plan?

It explains the overall approach to testing, including types of tests, techniques, and tools to be used, ensuring everyone understands how testing will be done.

intermediate

What role does the 'Risks and Contingencies' section play in a test plan?

It identifies possible risks that could affect testing and plans to handle them, helping to avoid surprises and delays.

Which section of a test plan describes the schedule and deadlines for testing activities?

A Test Strategy

B Test Items

C Test Schedule

D Risks and Contingencies

The Test Schedule section outlines when testing tasks will happen and their deadlines.

What does the 'Test Plan Identifier' section usually contain?

A Unique name or number for the test plan

B List of test cases

C Bug reports

D Test environment details

The Test Plan Identifier gives a unique name or number to the test plan for easy reference.

Which section explains the tools and techniques used for testing?

A Test Items

B Test Strategy

C Test Schedule

D Resources

The Test Strategy section describes the approach, tools, and techniques for testing.

Why include a 'Resources' section in a test plan?

A To list the software features

B To schedule test execution

C To describe the testing approach

D To identify people, hardware, and software needed

The Resources section lists all people, hardware, and software needed for testing.

What is the purpose of the 'Risks and Contingencies' section?

A To identify potential problems and backup plans

B To assign tasks

C To describe test environment

D To list test cases

This section helps prepare for possible problems and how to handle them.

Describe the main sections you would include in a test plan and their purpose.

Think about what information testers and managers need to organize testing.

Explain why having a clear test strategy is important in a test plan.

Consider how testers know what to do and how to do it.

Practice

1. Which section of a test plan describes what the testing aims to achieve?

easy

A. Test deliverables

B. Test schedule

C. Test environment

D. Test objectives

Solution

1. Step 1: Understand the purpose of test objectives

   Test objectives explain the goals and what the testing should accomplish.

2. Step 2: Compare with other sections

   Test schedule is about timing, environment is about setup, deliverables are outputs, so they don't describe goals.

3. Final Answer:

   Test objectives -> Option D

4. Quick Check:

   Goals = Test objectives [OK]

Hint: Objectives always state the testing goals clearly [OK]

Common Mistakes:

• Confusing schedule with objectives
• Mixing environment setup with goals
• Thinking deliverables define objectives

2. Which of the following is the correct way to list sections in a test plan?

easy

A. Objectives, Scope, Schedule, Resources

B. Code, Bugs, Fixes, Deployment

C. Design, Development, Testing, Release

D. Requirements, Coding, Debugging, Testing

Solution

1. Step 1: Identify typical test plan sections

   Common sections include objectives, scope, schedule, and resources.

2. Step 2: Eliminate unrelated options

   Options A, C, and D list software development phases or activities, not test plan sections.

3. Final Answer:

   Objectives, Scope, Schedule, Resources -> Option A

4. Quick Check:

   Test plan sections = B [OK]

Hint: Test plan sections focus on planning, not coding steps [OK]

Common Mistakes:

• Confusing development phases with test plan sections
• Listing activities instead of plan components
• Mixing testing with coding tasks

3. Given the test plan snippet:

Section: Test Scope
Includes: Login module, Payment module
Excludes: User profile module

What does this tell you about testing?

medium

A. Only Login and Payment modules will be tested

B. All modules including User profile will be tested

C. User profile module is the main focus

D. No modules will be tested

Solution

1. Step 1: Understand 'Includes' and 'Excludes' in scope

   Includes means what will be tested; excludes means what will not be tested.

2. Step 2: Apply to given modules

   Login and Payment modules are included, so they will be tested; User profile is excluded, so it won't be tested.

3. Final Answer:

   Only Login and Payment modules will be tested -> Option A

4. Quick Check:

   Scope includes = tested modules [OK]

Hint: Includes = test these; Excludes = skip these [OK]

Common Mistakes:

• Assuming excluded modules are tested
• Ignoring the scope section
• Confusing includes and excludes

4. A test plan section reads:

Test Schedule:
Start Date: 2024-05-01
End Date: 2024-04-30

What is wrong here?

medium

A. Dates are in wrong format

B. End date is before start date

C. Schedule section should not have dates

D. Start date should be after end date

Solution

1. Step 1: Check the dates in schedule

   Start date is May 1, 2024; end date is April 30, 2024.

2. Step 2: Compare dates logically

   End date cannot be before start date; this is a logical error in the schedule.

3. Final Answer:

   End date is before start date -> Option B

4. Quick Check:

   End date < Start date = Error [OK]

Hint: End date must be after start date [OK]

Common Mistakes:

• Ignoring date order
• Thinking format is wrong when it is correct
• Assuming schedule can't have dates

5. You need to create a test plan for a new app. Which combination of sections best ensures clear communication and smooth testing?

hard

A. Design Specs, Coding Standards, Test Scripts, Release Notes

B. Code Review, Bug List, Deployment Plan, User Manual

C. Objectives, Scope, Schedule, Resources, Risks, Deliverables

D. Marketing Plan, Sales Targets, Customer Feedback, Support Contacts

Solution

1. Step 1: Identify key test plan sections for clarity

   Objectives, scope, schedule, resources, risks, and deliverables cover goals, coverage, timing, people, potential problems, and outputs.

2. Step 2: Eliminate unrelated options

   Options A, B, and D focus on development, documentation, or business, not test planning.

3. Final Answer:

   Objectives, Scope, Schedule, Resources, Risks, Deliverables -> Option C

4. Quick Check:

   Complete test plan = Objectives, Scope, Schedule, Resources, Risks, Deliverables [OK]

Hint: Include goals, scope, timing, people, risks, and outputs [OK]

Common Mistakes:

• Confusing test plan with development or marketing documents
• Missing risk or deliverables sections
• Ignoring resource planning