antd-test-review

Check whether the expected value comes from an independent source like documentation, issue descriptions, or DOM semantics. If the assertion can only be derived from reading the production code, the test likely re-proves the implementation and should be flagged as low-value.

A test is low value when its expected output is computed from the same code path it tests, when it asserts private helpers or internal state, or when existing tests like mountTest and rtlTest already cover the same contract with similar props combinations.

CSS property assertions like toHaveStyle or toHaveClass are treated as low-value by default unless they correspond to a documented public contract. Prefer asserting on DOM structure, text content, ARIA attributes, or user-observable behavior instead.

When a test computes its expected value from the same implementation it exercises, it will always pass regardless of correctness. This creates false confidence and fails to catch regressions because the assertion and the code share the same logic.

Rewrite when the test intent targets a real user-facing behavior but the assertion method locks onto implementation details. Replace style or class assertions with DOM, role, or callback-based assertions that verify the same contract externally.