๐ Simple and complete DOM testing utilities that encourage good testing practices.
Reliability breakdown
Component scores measured daily from GitHub activity (2026-07-18).
Activity on 0 of 90 tracked days in the last 90 and 0 of 30 in the last 30.
Merged 0 of 0 PRs opened and closed 0 of 0 issues opened over the last 90 tracked days โ PR flow carries 55% of this component, issue flow 45%.
0 releases in the last 180 days, 0 in the last 90 and 0 in the last 30 โ a steady cadence scores highest.
Last push 250 days ago โ freshness decays as pushes age (roughly halves every 83 days without a push).
Open-issue load isn't tracked for this repo yet.
Modeled โ lower is better; concentration of commits in few maintainers. Contributors graph
Topics
Jump into the topic listings this repository belongs to.
DOM Testing Library is a JavaScript testing utility that queries and interacts with DOM nodes in ways similar to user behavior. It provides helpers for rendering-independent assertions, event simulation, and asynchronous UI checks, and it can pair with frameworks like React, Vue, or plain DOM code. It is commonly used in frontend unit and integration tests for component-driven applications.
Join the conversation
Share what you know about dom-testing-library โ write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting dom-testing-library.
Project Q&A
Browse implementation threads tied directly to testing-library/dom-testing-library. Each question links through to the full answer page.
Be the first to ask how teams run dom-testing-library in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses dom-testing-library โ a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post