testing-library/dom-testing-library

🐙 Simple and complete DOM testing utilities that encourage good testing practices.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 20 minutes ago
Added to GitGenius on September 20th, 2026
Created on April 6th, 2018
Open Issues & Pull Requests: 131 (+0)
GitHub issues: Enabled
Number of forks: 474
Total Stargazers: 3,333 (+0)
Total Subscribers: 30 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 36
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 973 days
Stale 30+ days: 35
Stale 90+ days: 32

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (5)
  • bug (2)
  • needs discussion (2)
  • aria-query (1)
  • documentation (1)
  • needs investigation (1)
  • needs more information (1)
  • released (1)

Most active issues this week

Detailed Description

DOM Testing Library is a testing utility library that provides simple and complete tools for testing DOM nodes in JavaScript applications.

The library addresses the problem of writing maintainable tests that focus on user behavior rather than implementation details. When tests rely on internal component structure, refactoring breaks them even when functionality remains unchanged. DOM Testing Library solves this by providing utilities that query the DOM in ways similar to how users find elements on a page, encouraging tests that resemble actual software usage. The approach centers on a core principle: the more tests resemble how software is used, the more confidence they provide.

The tool suits developers who want their test suites to remain stable through component refactors and who prioritize testing from the user's perspective. It works with DOM nodes whether simulated through JSDOM in Jest or in actual browsers, making it applicable across different testing environments. The library is lightweight and focuses on exposing only methods that encourage tests closely resembling real web page usage.

The project maintains active development with consistent engagement on pull requests and community contributions. The codebase has established code coverage standards that are actively monitored. The project operates under a welcoming code of conduct and maintains an active community channel for discussion and support.