Test the contract users rely on

Developer bridge: troubleshooting applied to testing
Original starter lesson / sources checked 2026-09-30

Prefer tests of visible behavior over implementation details. Labels and roles make interactions closer to how users navigate.

Give tests independent data and wait for expected states. Fixed sleeps can be too short on slow runs and unnecessarily long on fast runs.

Include keyboard navigation, error states, and a production-build smoke check. Automated accessibility rules are useful but incomplete.

Hands-on lab

Test a local form with an invalid value and assert its visible error.
Repeat using the keyboard and check where focus returns after closing a dialog.

Put the lesson to work

Original exam-style practice. Choose the best answer for the stated scenario.

1. Which assertion best tests a user-facing validation requirement?

The component uses two hooksThe function name is shortThe CSS bundle has an exact byte countThe invalid submission shows the expected error message

2. A browser test is flaky because it waits a fixed interval for data. What is a better approach?

Wait for the expected visible state with a retrying assertionIncrease every sleep to one minuteRemove every assertionRun until it passes once

Go deeper

Official CompTIA scope and exam information WWADD Move: Test the behavior users depend on

Independent practice aligned to selected topics. No endorsement, actual exam items, or pass guarantee. Verify your exam version and use the full official objectives for complete preparation.