Sebastian "Sebbie" Silbermann

If you want to optimize tests for performance go through these steps until you're satisfied. They're ordered by their confidence impact (lower impact, higher ranked) then perf impact (higher impact,...

> though I think I'd prefer to try another query before testIDs. I think it makes sense to add this to the docs. Definitely! It was easier to say since...

> I would definitely try item 3 from @eps1lon's checklist for this particular case - the visibility calculation is expensive in large DOM trees To touch on another potential optimization...

> I just want to stress this is nothing to do with timers. Everything is mocked. Why are you using `waitFor` if everything is mocked? If everything is mocked a...

> I did some comparison fetching the exact same element using getByText usually takes around 200~300ms, but with getByRole it takes upwards of 40 seconds!!! @shan-du Please share a reproducible...

I'm all for it 👍🏻 Note that access to `process.env.* ` still needs to be guarded since it's not defined in browsers. I would prefer using just `COLORS=false`. That leaves...

:tada: This fix is included in version 8.18.0 :tada: The release is available on: - [npm package (@latest dist-tag)](https://www.npmjs.com/package/@testing-library/dom/v/8.18.0) - [GitHub release](https://github.com/testing-library/dom-testing-library/releases/tag/v8.18.0)

Thanks for the detailed description. Could you expand on how assistive technology like screen readers discover these elements? Is there any specification for `` with regard to the a11y tree?

If you're asking to search for `status` by their accessible name then the spec has a pretty clear answer. But it seems to me you want to search by what...

Would it make more sense to use a [RegExp](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp) for the `name` then? I thought we already support this. If not then I would rather allow a regular expression than...