Challenge 3: Why the Convergence Claim Matters More — Possible Solution
====================================================================

"React Testing Library is a good tool" is a claim about ONE specific
library, tied to one specific framework — its truth says nothing
directly about what happens if a developer ever needs to test code in
Vue, Angular, or Svelte instead. Someone who only internalized "RTL is
good" has, strictly speaking, only learned facts about a single
library's API surface.

"Component-based UI testing has converged on one underlying philosophy
across frameworks" is a much stronger and more USEFUL claim because it
identifies something that TRANSFERS: query by role/text/label, fire
realistic events, assert on outcomes a real user would notice — a way
of THINKING about what makes a test good, independent of which
specific function names or setup ceremony a particular framework's
tool happens to require. This chapter demonstrated this concretely:
@testing-library/vue and @testing-library/svelte use almost the exact
same getByRole/getByText/fireEvent vocabulary as React's version, and
even Angular's more ceremonial TestBed setup is ultimately just
scaffolding in front of the same underlying idea, once
@testing-library/angular is used.

WHAT THIS TELLS ME ABOUT TRANSFERABLE SKILLS: the actual skill built
across Chapters 1-6 of this course — recognizing what makes a test
resistant to refactoring, knowing to query by role instead of CSS
class, understanding why absence-checking needs queryBy instead of
getBy — is NOT React-specific knowledge that has to be relearned from
scratch for a different framework. Learning to test well in one
component-based framework is, to a large degree, learning to test well
in ALL of them, with only the specific setup syntax (and, for Angular,
the DI-driven ceremony) left to pick up separately — a genuinely more
valuable and durable takeaway than mastery of one library's specific
API alone.