Bug tracking and fixing in Intro to Computing - Draw & Build Visually

Draw This - beginner

Draw a flowchart that shows the process of bug tracking and fixing in a software project. Start from identifying a bug, then reporting it, assigning it to a developer, fixing the bug, testing the fix, and finally closing the bug if the fix is successful.

10 minutes

Hint 1

Hint 2

Hint 3

Hint 4

Grading Criteria

Start and End oval symbols present

Process steps shown as rectangles

Decision point shown as diamond with Yes/No branches

Flow arrows correctly connect steps

Loop from failed test back to fixing step

Clear labeling of each step

Solution

  _______                 
 /       \                
|  Start  |               
 \_______/                
     |                    
     v                    
  _______________         
 | Identify bug  |         
  ---------------         
     |                    
     v                    
  _______________         
 | Report bug   |          
  ---------------         
     |                    
     v                    
  _______________         
 | Assign bug   |          
  ---------------         
     |                    
     v                    
  _______________         
 | Fix bug      |          
  ---------------         
     |                    
     v                    
  _______________         
 | Test fix     |          
  ---------------         
     |                    
     v                    
  _______________         
 | Is fix       |         
 | successful?  |          
  ---------------         
    /   \                 
   /     \                
  v       v               
 Yes     No               
  |       |               
  v       |               
 _______  |               
| Close | |               
| bug   | |               
 \_____/  |               
   |     |               
   v     |               
  _____  |               
 | End | |               
  -----  |               
         |               
         v               
   _______________      
  | Return to fix |      
  | bug          |      
   ---------------      
         |              
         v              
      (loops back to)   
      Fix bug step      

This flowchart starts with Start and moves to Identify bug, which means noticing a problem in the software. Then it goes to Report bug, where the bug is recorded in a tracking system. Next, the bug is Assigned to a developer who will fix it.

The developer works on Fix bug. After the fix, the software is Tested to check if the bug is really fixed. A decision diamond asks Is fix successful?

If yes, the bug is Closed and the process ends. If no, the flow returns to Fix bug to try again. This loop continues until the bug is fixed and closed.

Variations - 2 Challenges

[intermediate] Draw a flowchart for bug tracking and fixing that includes an additional step for 'Code review' after fixing the bug and before testing the fix.

[advanced] Draw a detailed flowchart for bug tracking and fixing that includes steps for 'Bug prioritization' after reporting the bug, and 'User confirmation' after closing the bug.

Practice

1. What is the main purpose of bug tracking in software development?

easy

A. To find and fix errors in the software

B. To add new features to the software

C. To design the user interface

D. To write documentation for users

Solution

1. Step 1: Understand the role of bug tracking

   Bug tracking is used to identify and keep track of errors or problems in software.

2. Step 2: Differentiate from other tasks

   Adding features, designing UI, and writing documentation are separate tasks from bug tracking.

3. Final Answer:

   To find and fix errors in the software -> Option A

4. Quick Check:

   Bug tracking = find and fix errors [OK]

Hint: Bug tracking = finding and fixing errors [OK]

Common Mistakes:

• Confusing bug tracking with adding features
• Thinking bug tracking is for UI design
• Mixing bug tracking with writing documentation

2. Which of the following is the correct way to report a bug?

easy

A. The app crashes when I click the 'Save' button. Steps to reproduce: 1. Open app 2. Click 'Save' 3. Observe crash.

B. The app is bad and doesn't work.

C. Fix the bug in the code immediately.

D. Add more features to the app.

Solution

1. Step 1: Identify a good bug report

   A good bug report clearly describes the problem and how to reproduce it.

2. Step 2: Compare options

   The app crashes when I click the 'Save' button. Steps to reproduce: 1. Open app 2. Click 'Save' 3. Observe crash. gives clear steps and describes the crash. Other options are vague or unrelated.

3. Final Answer:

   The app crashes when I click the 'Save' button. Steps to reproduce: 1. Open app 2. Click 'Save' 3. Observe crash. -> Option A

4. Quick Check:

   Clear bug report = detailed steps [OK]

Hint: Good bug reports include clear steps to reproduce [OK]

Common Mistakes:

• Writing vague bug descriptions
• Confusing bug reporting with fixing
• Reporting unrelated feature requests as bugs

3. Consider this code snippet that causes a bug:

def divide(a, b):
    return a / b

result = divide(10, 0)
print(result)

What will happen when this code runs?

medium

A. It will print 10

B. It will cause a runtime error (division by zero)

C. It will print 0

D. It will print None

Solution

1. Step 1: Analyze the divide function call

   The function tries to divide 10 by 0, which is mathematically undefined.

2. Step 2: Understand Python's behavior on division by zero

   Python raises a ZeroDivisionError at runtime when dividing by zero.

3. Final Answer:

   It will cause a runtime error (division by zero) -> Option B

4. Quick Check:

   Division by zero = runtime error [OK]

Hint: Division by zero causes runtime error in Python [OK]

Common Mistakes:

• Assuming division by zero returns 0
• Thinking it returns None
• Expecting the program to continue without error

4. You have this buggy code:

def find_max(numbers):
    max_num = 0
    for num in numbers:
        if num > max_num:
            max_num = num
    return max_num

print(find_max([-5, -2, -10]))

What is the bug and how to fix it?

medium

A. Remove the for loop

B. Change '>' to '<' in the if condition

C. Return min_num instead of max_num

D. Initialize max_num to first list element instead of 0

Solution

1. Step 1: Understand the bug with negative numbers

   Initializing max_num to 0 causes wrong result when all numbers are negative because 0 is greater than all negatives.

2. Step 2: Fix by initializing max_num to first element

   Set max_num = numbers[0] so comparison starts correctly with actual list values.

3. Final Answer:

   Initialize max_num to first list element instead of 0 -> Option D

4. Quick Check:

   Start max_num with first element for correct max [OK]

Hint: Initialize max with first list item, not zero [OK]

Common Mistakes:

• Assuming zero is always smallest
• Changing comparison direction incorrectly
• Removing loop instead of fixing initialization

5. A team uses a bug tracking tool to manage issues. They notice some bugs are marked 'fixed' but reappear later. What is the best way to prevent this?

hard

A. Assign bugs to multiple developers at once

B. Ignore bugs that reappear after fixing

C. Add thorough testing and verify fixes before closing bugs

D. Close bugs immediately after code change

Solution

1. Step 1: Understand why bugs reappear

   Bugs reappear if fixes are not properly tested or verified before closing.

2. Step 2: Implement thorough testing and verification

   Testing ensures the bug is truly fixed and prevents regression.

3. Final Answer:

   Add thorough testing and verify fixes before closing bugs -> Option C

4. Quick Check:

   Test fixes before closing bugs to prevent reappearance [OK]

Hint: Test fixes carefully before closing bugs [OK]

Common Mistakes:

• Closing bugs without testing
• Ignoring recurring bugs
• Assigning bugs to many developers causing confusion