Defect lifecycle in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to name the initial state of a defect after it is found.

Testing Fundamentals

defect_state = "[1]"  # Initial state when a defect is found

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

AOpen

BClosed

CRejected

DDeferred

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'Closed' because it sounds final, but defects start as 'Open'.

The initial state of a defect after it is found is called Open.

2fill in blank

medium

Complete the code to show the state when a defect is fixed by developers.

Testing Fundamentals

defect_state = "[1]"  # State after defect is fixed

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

ADeferred

BOpen

CRejected

DFixed

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'Closed' too early before retesting.

When developers fix a defect, its state changes to Fixed.

3fill in blank

hard

Fix the error in the code to represent the state when a defect is not accepted.

Testing Fundamentals

defect_state = "[1]"  # State when defect is invalid or not accepted

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

ARejected

BFixed

CClosed

DOpen

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'Rejected' with 'Closed'.

A defect that is invalid or not accepted is marked as Rejected.

4fill in blank

hard

Fill both blanks to complete the defect lifecycle transition code.

Testing Fundamentals

if defect_state == "Open":
    defect_state = "[1]"  # Developer fixes the defect
elif defect_state == "[2]":
    defect_state = "Closed"  # Tester closes after retest

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

AFixed

BRejected

COpen

DDeferred

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up 'Rejected' and 'Open' states.

After 'Open', the defect moves to 'Fixed' when developers fix it. Then from 'Fixed' (tester retesting), it can move to 'Closed' if retest passes.

5fill in blank

hard

Fill all three blanks to complete the defect lifecycle dictionary comprehension filtering defects by state.

Testing Fundamentals

defects = {id: state for id, state in defect_list.items() if state == "[1]" or state == "[2]" or state == "[3]"}

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

AOpen

BFixed

CRejected

DClosed

Attempts:

3 left

💡 Hint

Common Mistakes

Including 'Rejected' which is not part of active lifecycle filtering.

This code filters defects that are either 'Open', 'Fixed', or 'Closed' states, which are common active or resolved states in the lifecycle.

Practice

1. Which state in the defect lifecycle indicates that a bug has been found but not yet assigned to a developer?

easy

A. New

B. Fixed

C. Retest

D. Closed

Solution

1. Step 1: Understand the meaning of 'New' state

   The 'New' state means the defect is just reported and has not been assigned yet.

2. Step 2: Compare with other states

   'Fixed' means the bug is corrected, 'Retest' means testing the fix, and 'Closed' means the bug is resolved and accepted.

3. Final Answer:

   New -> Option A

4. Quick Check:

   New = Bug found but unassigned [OK]

Hint: New means just found, not assigned yet [OK]

Common Mistakes:

• Confusing 'New' with 'Open' or 'Assigned'
• Thinking 'Fixed' means bug is new
• Mixing 'Retest' with initial bug discovery

2. Which of the following is the correct order of states in a typical defect lifecycle?

easy

A. New -> Assigned -> Open -> Fixed -> Retest -> Closed

B. Fixed -> New -> Assigned -> Open -> Retest -> Closed

C. New -> Open -> Assigned -> Fixed -> Closed -> Retest

D. Assigned -> New -> Open -> Fixed -> Retest -> Closed

Solution

1. Step 1: Recall the standard defect lifecycle sequence

   The typical order is New (reported), Assigned (developer assigned), Open (work started), Fixed (bug fixed), Retest (testing fix), Closed (bug resolved).

2. Step 2: Match the options with this sequence

   New -> Assigned -> Open -> Fixed -> Retest -> Closed matches the correct order exactly; others have states out of order.

3. Final Answer:

   New -> Assigned -> Open -> Fixed -> Retest -> Closed -> Option A

4. Quick Check:

   Lifecycle order = B [OK]

Hint: Follow the bug from report to closure in order [OK]

Common Mistakes:

• Mixing 'Assigned' and 'Open' order
• Placing 'Fixed' before 'Assigned'
• Confusing 'Retest' and 'Closed' positions

3. Consider this defect lifecycle snippet:

defect_states = ['New', 'Assigned', 'Open', 'Fixed', 'Retest', 'Closed']
current_state = 'Fixed'
next_state = defect_states[defect_states.index(current_state) + 1]
print(next_state)

What will be the output?

medium

A. Fixed

B. Retest

C. Open

D. Closed

Solution

1. Step 1: Find the index of 'Fixed' in the list

   'Fixed' is at index 3 in defect_states list.

2. Step 2: Calculate next_state using index + 1

   Index 3 + 1 = 4, so next_state = defect_states[4] which is 'Retest'.

3. Final Answer:

   Retest -> Option B

4. Quick Check:

   Next after Fixed = Retest [OK]

Hint: Index +1 gives next lifecycle state [OK]

Common Mistakes:

• Choosing 'Closed' instead of 'Retest'
• Confusing index positions
• Assuming current_state prints itself

4. A tester reports a defect and marks it as 'Closed' immediately without retesting. What is the likely issue in this defect lifecycle process?

medium

A. Opening defect after fixing

B. Assigning defect before it is New

C. Reopening defect without fixing

D. Skipping the Retest phase

Solution

1. Step 1: Understand the defect lifecycle phases

   After fixing, the defect should be retested before closing to confirm the fix.

2. Step 2: Identify the problem with skipping Retest

   Marking as 'Closed' without retesting skips verification, risking unresolved bugs.

3. Final Answer:

   Skipping the Retest phase -> Option D

4. Quick Check:

   Retest must happen before Close [OK]

Hint: Always retest before closing a defect [OK]

Common Mistakes:

• Closing defect without verification
• Confusing 'Closed' with 'Fixed'
• Ignoring defect assignment order

5. A defect is marked as 'Reopened' after failing retest. Which of the following best describes the next correct step in the defect lifecycle?

hard

A. Mark the defect as 'New' again and wait for retest

B. Close the defect immediately as it failed retest

C. Assign the defect back to the developer for fixing

D. Skip fixing and move to 'Retest' again

Solution

1. Step 1: Understand 'Reopened' state meaning

   'Reopened' means the defect was fixed but failed retesting, so it needs fixing again.

2. Step 2: Determine the next lifecycle step

   The defect should be assigned back to the developer to fix the issue properly before retesting.

3. Final Answer:

   Assign the defect back to the developer for fixing -> Option C

4. Quick Check:

   Reopened = Assign to developer [OK]

Hint: Reopened defects go back to developer for fix [OK]

Common Mistakes:

• Closing defect after failed retest
• Resetting defect to 'New' incorrectly
• Skipping fix and retesting again