tape-testing/tape

tap-producing test harness for node and browsers

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 11th, 2026
Created on November 25th, 2012
Open Issues & Pull Requests: 40 (+0)
GitHub issues: Enabled
Number of forks: 304
Total Stargazers: 5,796 (+0)
Total Subscribers: 62 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 16.4 hours
90th percentile: 43.2 hours
Tracked items: 11

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 934 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

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

Top labels

  • question (3)
  • enhancement (1)
  • semver-minor: new stuff (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

tape is a TAP-producing test harness for Node and browsers.

tape solves the problem of running tests in a way that produces standardized TAP output, which can be consumed by other tools and is human-readable. It works by requiring tape in test files and running them through Node's standard mechanisms or through the tape binary, which supports globbing patterns for file discovery. The tool includes a preloading feature via the -r or --require flag, allowing modules like Babel to be loaded before tests execute, enabling features such as JIT compilation.

tape is suited for projects that want a minimal, standards-based testing approach. It works in both Node and browser environments and integrates well with the broader ecosystem of TAP consumers. The project maintains a deliberately minimal core, with additional features typically added through separate modules rather than built into tape itself. Pretty reporters and other enhancements are available as separate npm packages that consume tape's TAP output.

Development activity centers on questions and enhancement requests, with work focused on adding new features at the minor version level. The project maintains a steady stream of community engagement through its issue tracker while preserving its lean architectural philosophy.