Selenium WebDriver Research & Evidence-Based Practice 3

Question 1

In Selenium research, which approach to handling StaleElementReferenceException is considered the most robust?

Accepted Answer

Re-locating the element just before each interaction using a fresh WebDriver.findElement() call

Answer

Re-fetching the element reference immediately before use ensures the reference points to the current DOM state.

Question 2

Evidence shows that Selenium tests integrated into CI/CD pipelines deliver the most value when run at which stage?

Accepted Answer

After every code commit as part of the pull request validation gate

Answer

Running on every commit provides immediate feedback to developers while the context of the change is fresh.

Question 3

Which research-supported screenshot strategy in Selenium provides the highest debugging value?

Accepted Answer

Capturing screenshots automatically on test failure with the failing step context

Answer

Failure-triggered screenshots capture the UI state at the exact moment of failure, giving engineers actionable diagnostic context.

Question 4

Studies on Selenium test maintenance show that tests written without explicit assertions on expected state most commonly lead to:

Accepted Answer

False positives — tests pass even when the application is broken

Answer

Without assertions, Selenium will complete navigation and interactions without verifying outcomes, masking application defects.

Question 5

Research into cross-browser testing recommends which prioritization strategy when browser coverage must be limited by budget?

Accepted Answer

Prioritize browsers by actual user traffic share from analytics data

Answer

Analytics data ensures testing effort is proportional to real user impact, maximizing defect detection for the audience.

Selenium WebDriver Practice Test