A tester writes automated tests that check login functionality. Later, the login page UI changes, breaking the tests. How can the tester improve test design to reduce such breakage?

hard📝 Application Q9 of 15

Testing Fundamentals - Why Software Testing Matters

ATest only manually to avoid automation issues.

BUse stable locators like IDs or data attributes instead of text labels.

CAvoid updating tests after UI changes.

DHardcode all element paths to ensure exact matches.

Step-by-Step Solution

Solution:

Step 1: Understand cause of test breakage
Tests break when locators rely on unstable UI elements like text labels.
Step 2: Choose better locator strategy
Using stable attributes like IDs or data-* attributes reduces breakage.
Final Answer:
Use stable locators like IDs or data attributes instead of text labels. -> Option B
Quick Check:
Stable locators = fewer test breaks [OK]

Quick Trick: Use stable element locators in tests [OK]

Common Mistakes:

Hardcoding fragile locators
Ignoring test maintenance
Avoiding automation due to UI changes

Master "Why Software Testing Matters" in Testing Fundamentals

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Trace Try Challenge Automate Recall Frame

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Testing Fundamentals Quizzes

A tester writes automated tests that check login functionality. Later, the login page UI changes, breaking the tests. How can the tester improve test design to reduce such breakage?

Step 1: Understand cause of test breakage

Step 2: Choose better locator strategy

Final Answer:

Quick Check:

Want More Practice?