Selenium WebDriver Case Studies & Practical Application 5

Question 1

An e-commerce site applies discount codes via an API call triggered on blur of the coupon field. Tests verify the wrong final price. What is the fix?

Accepted Answer

After typing the coupon, trigger blur explicitly with Actions or Tab key, then wait for the price element to update before asserting

Answer

Explicitly triggering blur (Tab key or Actions.click elsewhere) fires the API call; an explicit wait on the updated price element ensures the assertion is timely.

Question 2

A test suite must clean up test data created during each run to avoid polluting the database. Which approach is recommended when using Selenium with a live staging DB?

Accepted Answer

Use @AfterEach/@After teardown to call an API or DB cleanup script that removes test records by a unique test-run ID

Answer

Teardown hooks that delete records tagged with a unique run ID ensure each test is isolated without affecting other records.

Question 3

A Selenium test clicks a button that triggers an async REST call and updates a counter on screen. The test asserts before the counter updates. What is the correct fix?

Accepted Answer

Use WebDriverWait to wait until the counter element's text changes to the expected value before asserting

Answer

WebDriverWait with textToBePresentInElement polls until the counter displays the expected value, reliably synchronizing with the async REST response.

Question 4

A team manages 300 Selenium tests across 10 modules. They want to re-run only failed tests without restarting the full suite. Which mechanism supports this in TestNG?

Accepted Answer

Use the testng-failed.xml generated after a run to re-execute only failed tests

Answer

TestNG automatically generates testng-failed.xml after a run; executing this file reruns only the failed tests without modifying source files.

Question 5

A team integrates Selenium tests into a Jenkins pipeline. Tests should block a deployment when more than 5% fail. How is this threshold configured?

Accepted Answer

Use the JUnit/TestNG results plugin in Jenkins to set an unstable/failure threshold on the test result percentage

Answer

Jenkins' JUnit plugin lets you configure unstable and failure thresholds based on the percentage of failed tests from the reported XML results.

Selenium WebDriver Practice Test

Selenium WebDriver Practice Test

Selenium WebDriver Case Studies & Practical Application 5