Moderate Testing Question 113 of 229

Why does React Testing Library discourage testing by CSS class?

Frontend Master · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: DATA SPLIT

Train 70%Val 15%Test 15%

Fit on train, tune on val, report on test once.

Simple meaning

Classes change during restyles even when the user experience did not.

1

WHY — Testing instead of guessing?

Why interviewers care about Testing:

They are checking judgment

on Testing.

A good answer names

the situation, the default choice, and one exception - that reads as experience.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

2

STEPS — What happens step by step?

Before you speak the answer, walk the interviewer through these steps:

  1. 1
    Classes change during restyles

    even when the user experience did not.

  2. 2
    Roles, labels, and text

    stay closer to what users and assistive tech see.

  3. 3
    Data-testid is a last

    resort when there is no accessible name.

  4. 4
    Give an example

    One tiny concrete case you can say aloud.

  5. 5
    Common mistake

    What juniors usually get wrong.

  6. 6
    Close

    When you pick this over the alternative.

3

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line
“Roles, labels, and text stay closer to what users and assistive tech see.”
Break into beats
Roleslabelsandtextstaycloser
Speaking order
2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

Classes change during restyles even when the user experience did not. Roles, labels, and text stay closer to what users and assistive tech see.

Chat with us