@TestingLib

Libraries, utilities, and tools to enable you to write tests that resemble the way your software is used. @ReactJS, @VueJS, @Cypress_IO, @angular, @fbjest, more

 your tests
testing-library.com
Joined April 2019
  • Tweets391
  • Following10
  • Followers10.8K
7Media
Testing Library retweeted
Corbin Crutchley
@crutchcorn11 Jan 2025
Heads up to anyone using JSDom for testing, I believe as of three days ago there was a change to some sub-deps that broke behavior for anyone upgrading their package lock: github.com/jsdom/cssstyle/is… I'm working on a fix right now
3
4
1
19
7,909
Testing Library retweeted
Wallaby Team
@wallabyjs7 Nov 2024
New Wallaby 2 feature: ✨ HTML highlighting for @TestingLib errors and screen.debug() output, styled with your editor theme 🎨 for easier, readable debugging. 🔍
4
11
1,503
Testing Library retweeted
Lenz Weber-Tronic@phry21 Oct 2024
I'm thrilled to finally announce the release of a new @testing-library, React RenderStream testing library. We have been using the underlying approach in over 500 Apollo Client tests for a year now, and it has given us a new level of confidence. (Link in next Post)
3
29
7
138
46,028
Heads up @TestingLib users 🐙 Due to multiple issues we've observed in the past releases, we've just released a new major of React Testing Library (16) that moves @testing-library/dom to a peer dependency. Keep in mind that you'll need to manually install DTL from that version.
2
3
20
7,895
It's official. @TestingLib is now THE testing solution for @reactjs. What a journey! react.dev/blog/2024/04/25/re…
React migration guide that says: Deprecated: react-test-renderer We are deprecating react-test-renderer because it implements its own renderer environment that doesn’t match the environment users use, promotes testing implementation details, and relies on introspection of React’s internals. The test renderer was created before there were more viable testing strategies available like React Testing Library, and we now recommend using a modern testing library instead. In React 19, react-test-renderer logs a deprecation warning, and has switched to concurrent rendering. We recommend migrating your tests to @testing-library/react or @testing-library/react-native for a modern and well supported testing experience.

ALT React migration guide that says: Deprecated: react-test-renderer We are deprecating react-test-renderer because it implements its own renderer environment that doesn’t match the environment users use, promotes testing implementation details, and relies on introspection of React’s internals. The test renderer was created before there were more viable testing strategies available like React Testing Library, and we now recommend using a modern testing library instead. In React 19, react-test-renderer logs a deprecation warning, and has switched to concurrent rendering. We recommend migrating your tests to @testing-library/react or @testing-library/react-native for a modern and well supported testing experience.

26
54
2
947
55,999
🚀 We released #Angular Testing Library v16 today With this update, you receive the latest specification updates for role/element mappings to align with WAI-ARIA 1.2. Why should you care? 🔎 better role support, including new roles ⚠️ existing queries might behave differently
1
19
1
67
5,895
🎉 🎉🎉 A new major version of React @TestingLib was released (15.0.0) - This release drops support for Node 14, Node 16 and most importantly, adds support for new ARIA roles defined as part of WAI-ARIA 1.2. If you have any feedback or issues, feel free to reach out.
2
6
1
34
4,407
Testing Library retweeted
Ernesto
@gnapse30 Jan 2024
Here's an opportunity to contribute to @TestingLib's jest-dom 🦉 and dive into the world of accessibility: Create the toBeActiveDescendant custom matcher. Your chance to learn and make a positive impact awaits. 🤝 Check it out github.com/testing-library/j…

toBeActiveDescendant · Issue #207 · testing-library/jest-dom

Describe the feature you'd like: I'm testing composite components that use aria-activedescendant to move focus. I would like to test whether some item is "virtually" focused or no...

github.com
5
13
8,629
We see this asked quite a lot: If you've migrated from Jest to Vitest and looking for the jest-dom equivalent for @vitest_dev, just edit your setup file 🦉
Use import '@testing-library/jest-dom/vitest' instead of import '@testing-library/jest-dom' to get jest-dom assertions in Vitest.

ALT Use import '@testing-library/jest-dom/vitest' instead of import '@testing-library/jest-dom' to get jest-dom assertions in Vitest.

14
74
9,505
🚨 Implementation detail 🚨 Lately, I've been seeing this pattern for testing async stuff. This pattern creates a new promise and awaits for it to resolve. This means we'll wait for all async operations to finish. Prefer @TestingLib waitFor with a meaningful assertion.
A bad example awaiting a new promise with a setImmediate vs a waitFor from testing-library with a meaningful assertion.

ALT A bad example awaiting a new promise with a setImmediate vs a waitFor from testing-library with a meaningful assertion.

1
2
18
4,972
✍️ Blogged: #Angular standalone components and Angular Testing Library make component tests easier timdeschryver.dev/blog/angul…

Angular standalone components and Angular Testing Library make component tests easier

Standalone components give you a better foundation to build on, as your Angular component becomes less affected by its internals. It doesn't matter if the component has its own template, or if it's...

timdeschryver.dev
2
22
58
7,199
This is a great write-up on a migration from enzyme to @TestingLib: blog.sentry.io/2023/02/23/se…
9
2
62
16,739
#Angular Testing Library v13 is released 🚀 This release contains: - more control over component Input properties - more control over CD - extra's for standalone components Thanks @antischematic for the ideas and help 🏆 github.com/testing-library/a…

Release v13.0.0 · testing-library/angular-testing-library

13.0.0 (2022-12-14) Features release v13 (#327) (6ae1363), closes #324 #325 #318 #326 #323 #328 #329 #330 #338 #339 #341 #342 #343 BREAKING CHANGES The render property ɵcomponentImports is not e...

github.com
10
42
React Testing Library v13 with support for React 18 is now released. Upgrade now if your app is using React 18. npmjs.com/package/@testing-l… Many thanks @sebsilbermann for the hard work on this release!
3
41
1
171
Testing Library retweeted
Philipp Fritsche@ph_fritsche10 Jan 2022
The documentation for @TestingLib's user-event has been updated. If you are actively working on a project, we recommend to switch to `v14-beta` now. 🚀 Check it out! 👇 testing-library.com/user-eve…
7
1
19
Testing Library retweeted
@belco.dev (bsky)@belcoDev25 Oct 2021
So eslint-plugin-testing-library v5 has been just released! Including support for ESLint v8. Make sure you check the breaking changes before upgrading: github.com/testing-library/e… Huge thanks to @MichaelDeBoey93 who really pushed things forward to get this new version published.

Release v5.0.0 · testing-library/eslint-plugin-testing-library

5.0.0 (2021-10-25) BREAKING CHANGES prefer-query-by-disappearance: prefer-query-by-disappearance is now enabled by default in all configs prefer-presence-queries: prefer-presence-queries is now en...

github.com
This Post is from an account that no longer exists. Learn more
8
16
React and react component testing have come a long way. I so agree with this article. Lets not use enzyme.js anymore 👋 piotrstaniow.pl/goodbye-enzy…

Time to say goodbye - Enzyme.js

The world has already moved - to React Testing Library

piotrstaniow.pl
4
38
199
Testing Library retweeted
Kent C. Dodds 🐨
@kentcdodds5 Jul 2021
Replying to @markdalgleish
Related: kentcdodds.com/blog/how-to-t…

How to test custom React hooks

Get confidence your custom React hooks work properly with solid tests.

kentcdodds.com
1
11
48
Testing Library retweeted
Ernesto
@gnapse11 Jun 2021
jest-dom v5.14.0 introduces two new matchers: - toHaveAccessibleName - toHaveAccessibleDescription Another step towards promoting the use of more semantic and accessible markup. Making sure you properly label and describe elements has never been easier. github.com/testing-library/j…

Release v5.14.0 · testing-library/jest-dom

5.14.0 (2021-06-11) Features toHaveAccessibleName and toHaveAccessibleDescription (#377) (87ffd2a)

github.com
2
26
3
158
Testing Library retweeted
Ernesto
@gnapse3 Jun 2021
Starting with v5.13.0 jest-dom has a new matcher toHaveErrorMessage. This is a big step in promoting the use of more semantic and accessible markup to flag errors in form elements. github.com/testing-library/j…
A screenshot of the README section documenting this new matcher in jest-dom: https://github.com/testing-library/jest-dom#tohaveerrormessage

ALT A screenshot of the README section documenting this new matcher in jest-dom: https://github.com/testing-library/jest-dom#tohaveerrormessage

1
4
22
Load more