Which approach best helps a non-technical stakeholder understand why a Selenium test suite requires maintenance after each UI change?
-
A
Show them the XPath locators that broke
-
B
Explain that tests are like step-by-step directions — when the road changes, the directions must be updated too
-
C
Give them access to the CI/CD pipeline logs
-
D
Send them a link to the Selenium documentation