With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js. Learn more →
Dom-testing-library Alternatives
Similar projects and alternatives to dom-testing-library based on common topics and language
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
angular-testing-library
🐙 Simple and complete Angular testing utilities that encourage good testing practices
-
cypress-testing-library
🐅 Simple and complete custom Cypress commands and utilities that encourage good testing practices.
-
javascript-testing-best-practices
📗🌐 🚢 Comprehensive and exhaustive JavaScript & Node.js testing best practices (July 2023)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
dom-testing-library reviews and mentions
- Buenas prácticas con Angular Testing Library
-
Problems with using `useFakeTimers('modern')` in a create-react-app (CRA) project with Jest 26 and Lodash's `debounce` function
I did some digging and it looks like testing-library/dom-testing-library recommended using jest-environment-jsdom-sixteen in its release notes for v7.0.0 because CRA was using an older version of Jest which provided an older version of jsdom that was missing support for things like MutationObservers and other modern web features. However, eventually CRA was updated to use the newer version of Jest, and this made using jest-environment-jsdom-sixteen unnecessary – and in this case actually harmful as it prevented me from using the new useFakeTimers('modern') functionality. Once I removed the --env=jsdom-sixteen line from the test script in package.json everything started working as I expected.
-
How to test a select element with React Testing Library
"xByRole" is the most "correct" one, but it is also really slow if you're rendering something complex. Just a heads up. See this github issue for more info.
-
Using RTL: getByRole is quite slow on simple tests
https://github.com/testing-library/dom-testing-library/issues/820#issuecomment-726936225
-
A note from our sponsor - SurveyJS
surveyjs.io | 20 Apr 2024
Stats
testing-library/dom-testing-library is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of dom-testing-library is JavaScript.