Tester mindset and thinking in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to print the first step a tester should take when starting a new testing task.

Testing Fundamentals

print("Step 1: Understand the [1]")

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

Atools

Bcode

Cbugs

Drequirements

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'code' or 'bugs' before understanding requirements.

The first step for a tester is to understand the requirements to know what to test.

2fill in blank

medium

Complete the code to show what a tester should do after finding a problem.

Testing Fundamentals

print("Next, a tester should [1] the problem clearly.")

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

Aignore

Breport

Chide

Dfix

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'fix' which is usually done by developers.

After finding a problem, a tester should report it clearly so developers can fix it.

3fill in blank

hard

Fix the error in the code that shows a tester's mindset to question assumptions.

Testing Fundamentals

if not [1]:
    print("Always question assumptions.")

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

Atrust

Bdoubt

Cignore

Daccept

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'doubt' which would invert the logic incorrectly.

The tester should question assumptions by checking if they trust them blindly or not.

4fill in blank

hard

Fill both blanks to complete the tester's checklist for thorough testing.

Testing Fundamentals

checklist = ["Understand [1]", "Design [2]"]

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

Arequirements

Bbugs

Ctest cases

Dtools

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing 'bugs' or 'tools' instead of 'requirements' or 'test cases'.

A tester must first understand requirements and then design test cases to check them.

5fill in blank

hard

Fill all three blanks to complete the tester's process for handling a bug.

Testing Fundamentals

bug = {"id": [1], "status": "[2]", "priority": "[3]"}

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

A101

Bopen

Chigh

Dclosed

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'closed' status or wrong id number.

The bug has an id of 101, its status is 'open', and its priority is 'high'.