Selenium Testing Framework Risk Assessment & Management 3

Question 1

Which practice reduces the risk of false positives caused by dynamic element IDs in Selenium tests?

Accepted Answer

Locating elements by stable data-testid attributes

Answer

Stable data-testid attributes are explicitly added for testing purposes and do not change with rendering logic, eliminating false positives from dynamic IDs.

Question 2

A Selenium Grid node is running an outdated operating system. What category of risk does this represent?

Accepted Answer

Infrastructure and security risk

Answer

Outdated OS versions on Grid nodes expose the test infrastructure to unpatched security vulnerabilities and compatibility failures.

Question 3

Which risk is associated with relying solely on Selenium end-to-end tests and skipping unit and integration tests?

Accepted Answer

Slow feedback loops and high debugging cost when failures occur

Answer

E2E-only strategies provide slow feedback and make it hard to pinpoint root causes; a layered testing pyramid reduces this risk.

Question 4

What risk does running Selenium tests in headless mode introduce compared to headed mode?

Accepted Answer

Some rendering and JavaScript behavior may differ, hiding UI bugs

Answer

Headless browsers may render CSS and execute JavaScript slightly differently, potentially masking visual defects that would appear in a real user's browser.

Question 5

A team stores Selenium test credentials in plain-text configuration files committed to version control. What risk does this create?

Accepted Answer

Credential exposure and potential unauthorized access

Answer

Committing credentials to version control exposes them to anyone with repository access, creating a significant security risk.

Selenium Testing Framework Practice Test

Selenium Testing Framework Practice Test

Selenium Testing Framework Risk Assessment & Management 3