Testing vs debugging distinction in Testing Fundamentals - Framework Approaches Compared

Framework Mode - Testing vs debugging distinction

Folder Structure of a Typical Testing Project

  testing-project/
  ├── tests/               # Automated test scripts
  │   ├── unit/            # Unit tests
  │   ├── integration/     # Integration tests
  │   └── e2e/             # End-to-end tests
  ├── src/                 # Application source code
  ├── debug/               # Debugging scripts and logs
  │   ├── logs/            # Logs collected during debugging
  │   └── scripts/         # Helper scripts for debugging
  ├── reports/             # Test execution reports
  ├── config/              # Configuration files
  └── utils/               # Utility functions for tests
  

Test Framework Layers

• Test Layer: Contains test cases that check if the software works as expected.
• Debug Layer: Contains tools and scripts to find and fix problems when tests fail.
• Utility Layer: Helper functions used by both tests and debugging scripts.
• Configuration Layer: Holds settings like environment details and credentials.
• Reporting Layer: Collects and shows results of tests to understand success or failure.

Configuration Patterns

Use separate config files for different environments (e.g., dev, test, prod). This helps tests run correctly in each place.

Store sensitive data like passwords securely, not in plain files. Use environment variables or secret managers.

Configure test settings (like browser type or timeout) in one place to easily change them without editing tests.

Test Reporting and CI/CD Integration

Test reports show which tests passed or failed. They help quickly spot problems.

Integrate tests into CI/CD pipelines to run tests automatically on every code change.

Debugging logs and error details should be linked to test failures to speed up problem fixing.

Best Practices for Testing vs Debugging

• Separate Concerns: Keep testing and debugging code in different folders to avoid confusion.
• Automate Testing: Write tests that run automatically to catch issues early.
• Use Logs Wisely: Collect detailed logs during test failures to help debugging.
• Clear Reporting: Make test reports easy to read and understand for quick feedback.
• Secure Configurations: Protect sensitive info and keep configs flexible for different environments.

Self Check Question

Where in this folder structure would you add a new script to help find why a test is failing?

Key Result

Testing checks if software works; debugging finds and fixes why it doesn't.

Practice

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

easy

A. To find bugs by checking if the software works as expected

B. To fix the cause of bugs in the code

C. To write new features for the software

D. To design the user interface

Solution

1. Step 1: Understand the role of testing

   Testing is about running the software to check if it behaves correctly and to find any bugs.

2. Step 2: Differentiate testing from debugging

   Debugging is about finding and fixing the cause of bugs, not just finding them.

3. Final Answer:

   To find bugs by checking if the software works as expected -> Option A

4. Quick Check:

   Testing = Find bugs [OK]

Hint: Testing finds bugs; debugging fixes bugs [OK]

Common Mistakes:

• Confusing testing with fixing bugs
• Thinking testing creates new features
• Mixing testing with design tasks

2. Which of the following best describes debugging?

easy

A. Writing code to add features

B. Finding and fixing the cause of bugs

C. Running tests to find errors

D. Designing test cases

Solution

1. Step 1: Define debugging

   Debugging means investigating the cause of bugs and correcting them in the code.

2. Step 2: Compare with other options

   Running tests is testing, not debugging. Writing features and designing tests are different tasks.

3. Final Answer:

   Finding and fixing the cause of bugs -> Option B

4. Quick Check:

   Debugging = Fix bugs [OK]

Hint: Debugging fixes bugs, not just finds them [OK]

Common Mistakes:

• Confusing debugging with testing
• Thinking debugging is writing new code
• Mixing debugging with test design

3. Consider this scenario: A tester runs a test and finds the software crashes when clicking a button. What is the next step in debugging?

medium

A. Write more test cases for other buttons

B. Ignore the crash and continue testing

C. Analyze the code to find why the crash happens

D. Change the button label text

Solution

1. Step 1: Identify the testing result

   The test found a crash when clicking a button, indicating a bug.

2. Step 2: Understand debugging action

   Debugging means analyzing the code to find the cause of the crash and fix it.

3. Final Answer:

   Analyze the code to find why the crash happens -> Option C

4. Quick Check:

   Debugging = Analyze and fix bug [OK]

Hint: After finding bug, analyze code cause [OK]

Common Mistakes:

• Continuing testing without fixing bugs
• Ignoring bugs found during testing
• Changing unrelated UI elements

4. A developer writes code but the program crashes. Which step is part of debugging to fix this?

medium

A. Run tests to find if the program crashes

B. Write more features before fixing the crash

C. Ignore the crash and release the software

D. Check the error message and trace the code causing the crash

Solution

1. Step 1: Identify debugging task

   Debugging involves checking error messages and tracing code to find the cause of crashes.

2. Step 2: Eliminate incorrect options

   Running tests finds bugs but does not fix them. Writing features or ignoring crashes are wrong.

3. Final Answer:

   Check the error message and trace the code causing the crash -> Option D

4. Quick Check:

   Debugging = Trace and fix errors [OK]

Hint: Use error messages to trace bugs [OK]

Common Mistakes:

• Confusing testing with debugging
• Skipping error analysis
• Adding features before fixing bugs

5. A software tester finds a bug where the app crashes only when a specific input is given. What is the best combined approach to handle this?

hard

A. Write a test case for that input and then debug the code to fix the crash

B. Ignore the input and test other features

C. Fix the code without writing any test cases

D. Write test cases for all inputs except the problematic one

Solution

1. Step 1: Understand testing role

   Writing a test case for the specific input helps reproduce and confirm the bug.

2. Step 2: Understand debugging role

   Debugging the code to fix the crash addresses the root cause of the bug.

3. Step 3: Combine testing and debugging

   Both steps together ensure the bug is found, fixed, and verified.

4. Final Answer:

   Write a test case for that input and then debug the code to fix the crash -> Option A

5. Quick Check:

   Test to find + Debug to fix = Correct approach [OK]

Hint: Test to find bug, debug to fix bug [OK]

Common Mistakes:

• Skipping test case creation for bugs
• Fixing bugs without verifying
• Ignoring problematic inputs