Why evidence collection supports debugging in Selenium Python - Quick Recap

Recall & Review

beginner

What is evidence collection in debugging?

Evidence collection means gathering information like logs, screenshots, and error messages during test runs to understand what happened.

beginner

How does collecting screenshots help in debugging Selenium tests?

Screenshots show the exact state of the web page when a test fails, helping to see visual problems or unexpected page content.

beginner

Why are logs important for debugging automated tests?

Logs record step-by-step actions and errors, making it easier to find where and why a test failed.

intermediate

What role does evidence collection play in fixing bugs faster?

It provides clear clues about the problem, so developers spend less time guessing and more time fixing the issue.

intermediate

Can evidence collection prevent repeated test failures? How?

Yes, by understanding the root cause through collected evidence, tests can be improved or fixed to avoid the same failure again.

What type of evidence is most useful to see the exact page state during a Selenium test failure?

A Screenshot

B Log file

C Test script

D Database dump

Screenshots capture the visual state of the page at failure time, which logs or scripts cannot show.

Why are logs collected during automated tests?

A To record test steps and errors

B To speed up the test execution

C To change the test data

D To create screenshots

Logs help track what happened during the test, including errors and actions.

How does evidence collection support faster bug fixing?

A By making tests run slower

B By providing clear clues about the problem

C By hiding errors from developers

D By removing test cases

Clear clues reduce guesswork, helping developers fix bugs quickly.

Which of these is NOT a form of evidence collection in Selenium testing?

A Taking screenshots

B Saving logs

C Writing test scripts

D Capturing error messages

Writing test scripts is creating tests, not collecting evidence during test runs.

What can happen if you do NOT collect evidence during debugging?

A You get more screenshots

B Tests run faster

C Errors fix themselves

D It becomes harder to find the root cause of failures

Without evidence, debugging is guesswork and takes longer.

Explain why collecting screenshots and logs during Selenium test failures helps debugging.

Think about what each type of evidence shows you.

Describe how evidence collection can prevent repeated test failures.

Focus on how knowing the problem helps improve tests.

Practice

1. Why is collecting evidence like screenshots and logs important when debugging database tests in Selenium Python?

easy

A. It automatically fixes errors in the database.

B. It helps quickly find and fix problems by showing what happened during tests.

C. It replaces the need to write test cases.

D. It slows down the test execution and should be avoided.

Solution

1. Step 1: Understand the role of evidence collection

   Evidence like screenshots and logs capture the state and actions during tests, providing clues about failures.

2. Step 2: Connect evidence to debugging efficiency

   Having this information helps developers quickly identify where and why a problem happened, speeding up fixes.

3. Final Answer:

   It helps quickly find and fix problems by showing what happened during tests. -> Option B

4. Quick Check:

   Evidence collection = faster debugging [OK]

Hint: Remember: evidence shows what happened to fix issues fast [OK]

Common Mistakes:

• Thinking evidence slows tests
• Believing evidence replaces test cases
• Assuming evidence fixes errors automatically

2. Which of the following is the correct way to save a screenshot in Selenium Python during a database test?

easy

A. driver.capture('image.png')

B. driver.take_screenshot('image.png')

C. driver.screenshot_save('image.png')

D. driver.save_screenshot('image.png')

Solution

1. Step 1: Recall Selenium Python screenshot method

   The correct method to save a screenshot is save_screenshot on the driver object.

2. Step 2: Verify method names

   Other options like take_screenshot, capture, or screenshot_save are not valid Selenium methods.

3. Final Answer:

   driver.save_screenshot('image.png') -> Option D

4. Quick Check:

   Correct method = save_screenshot [OK]

Hint: Use driver.save_screenshot() to capture images [OK]

Common Mistakes:

• Using incorrect method names
• Confusing screenshot with capture
• Misspelling method names

3. Given this Selenium Python code snippet during a database test:

logs = driver.get_log('browser')
print(len(logs))

What does the output represent?

medium

A. The number of database rows returned by the query.

B. The number of screenshots taken.

C. The number of browser log entries collected during the test.

D. The number of errors fixed automatically.

Solution

1. Step 1: Understand driver.get_log('browser')

   This command fetches browser console logs collected during the test run.

2. Step 2: Interpret len(logs)

   Counting the logs with len(logs) gives how many log entries were captured.

3. Final Answer:

   The number of browser log entries collected during the test. -> Option C

4. Quick Check:

   len(logs) = count of browser logs [OK]

Hint: get_log('browser') returns browser console logs list [OK]

Common Mistakes:

• Confusing logs with database rows
• Thinking logs count screenshots
• Assuming logs fix errors

4. You wrote this code to save a screenshot during a database test:

driver.screenshot('test.png')

But it raises an error. What is the problem?

medium

A. The method name is incorrect; it should be save_screenshot.

B. The file extension .png is not supported.

C. Screenshots cannot be saved during database tests.

D. The driver object is missing a required argument.

Solution

1. Step 1: Check the method name used

   The method screenshot does not exist; the correct method is save_screenshot.

2. Step 2: Confirm file extension and usage

   PNG is a valid format and screenshots can be saved during tests; no missing arguments needed here.

3. Final Answer:

   The method name is incorrect; it should be save_screenshot. -> Option A

4. Quick Check:

   Correct method = save_screenshot [OK]

Hint: Use save_screenshot, not screenshot, to save images [OK]

Common Mistakes:

• Using wrong method name
• Thinking .png is invalid
• Assuming screenshots not allowed in DB tests

5. In a Selenium Python test for a database-driven web app, you want to collect evidence only when a test fails. Which approach best supports this?

hard

A. Use a try-except block to catch errors and save screenshots and logs only on failure.

B. Always save screenshots and logs regardless of test result to save time.

C. Skip evidence collection to speed up tests and rely on console messages.

D. Manually check the database after tests instead of collecting evidence.

Solution

1. Step 1: Understand conditional evidence collection

   Collecting evidence only on failure saves storage and focuses debugging efforts.

2. Step 2: Use try-except to detect failures

   A try-except block can catch exceptions during tests and trigger evidence saving only when errors occur.

3. Step 3: Evaluate other options

   Always saving wastes resources, skipping evidence loses info, and manual DB checks are slow and error-prone.

4. Final Answer:

   Use a try-except block to catch errors and save screenshots and logs only on failure. -> Option A

5. Quick Check:

   Try-except for conditional evidence = best practice [OK]

Hint: Save evidence only on failure using try-except [OK]

Common Mistakes:

• Saving evidence always wastes resources
• Skipping evidence loses debugging info
• Relying on manual DB checks is slow