Test plan structure in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the main section of a test plan.

Testing Fundamentals

test_plan = {
    'scope': 'Define what to test',
    'objectives': 'Set goals',
    'resources': 'List needed [1]'
}

Drag options to blanks, or click blank then click option'

Abugs

Btools

Cerrors

Dusers

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing resources with bugs or errors.

The 'resources' section lists the tools and people needed for testing.

2fill in blank

medium

Complete the code to specify the test schedule in the test plan.

Testing Fundamentals

test_plan['schedule'] = 'Timeline for testing activities including [1] and deadlines'

Drag options to blanks, or click blank then click option'

Abugs

Breports

Cerrors

Dmilestones

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'bugs' or 'errors' instead of schedule markers.

Milestones mark important points in the testing timeline.

3fill in blank

hard

Fix the error in the test plan section that defines test deliverables.

Testing Fundamentals

test_plan['deliverables'] = ['Test cases', 'Test reports', [1]]

Drag options to blanks, or click blank then click option'

A'Test logs'

B'Test errors'

C'Test bugs'

D'Test failures'

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing deliverables with bugs or errors.

Test logs are documents generated during testing and are part of deliverables.

4fill in blank

hard

Fill both blanks to complete the test plan's risk management section.

Testing Fundamentals

test_plan['risk_management'] = {
    'risks': [1],
    'mitigation': [2]
}

Drag options to blanks, or click blank then click option'

A['delays', 'bugs']

B['errors', 'failures']

C['avoidance', 'reduction']

D['testing', 'reporting']

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing risks with mitigation strategies.

Risks include delays and bugs; mitigation means avoiding or reducing them.

5fill in blank

hard

Fill all three blanks to complete the test plan's entry criteria section.

Testing Fundamentals

test_plan['entry_criteria'] = {
    'requirements_complete': [1],
    'environment_ready': [2],
    'test_data_available': [3]
}

Drag options to blanks, or click blank then click option'

ATrue

BFalse

CNone

D'Yes'

Attempts:

3 left

💡 Hint

Common Mistakes

Using False or None instead of True for criteria.

Entry criteria require all conditions to be true before testing starts.

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