Open source framework for managing unit and integration testing
active 2025-02-15 → 2026-01-01 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 321 days from 2025-02-15 to 2026-01-01. Pushes: 382 total, peak 64 in a day. Pull requests: 9 total, peak 6 in a day. Issues: 102 total, peak 19 in a day. Comments: 27 total, peak 13 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| TylerHanavan | 520 | 382 | 9 | 27 |
Recent activity
Latest issues, pull requests and releases
- Issue#84TylerHanavan2026-01-01 01:39allow for better error parsing when there is an error in the XXXTest.php file
- Issue#83TylerHanavan2026-01-01 01:39add flag to not run nested tsuite so there is not infinite recursion when testing tsuite with tsuite
- Issue#82TylerHanavan2025-03-29 22:50enable better way of accessing $TSUITE_TEST... variables instead of from environment variable file
- Issue#81TylerHanavan2025-03-29 20:17fatal error test only works if it is the last stage
- Issue comment#78TylerHanavan2025-03-29 18:31all output from shell actions is written to the test results file twice
- Issue#78TylerHanavan2025-03-29 18:31all output from shell actions is written to the test results file twice
- Issue comment#80TylerHanavan2025-03-29 18:30tables are getting dropped after test completes
- Issue#80TylerHanavan2025-03-29 18:30tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 18:28tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 18:24tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 18:19tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 18:16tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 18:14tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 18:12tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 18:11tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 18:09tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 18:08tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 18:06tables are getting dropped after test completes
- Issue comment#80TylerHanavan2025-03-29 17:58tables are getting dropped after test completes
- Issue#80TylerHanavan2025-03-29 17:50tables are getting dropped after test completes
- Issue#79TylerHanavan2025-03-29 17:44tests that fail for FATAL_ERROR when expected_outcome is FATAL_ERROR show as success, but their underlying function that had the FATAL_ERROR show failure
- Issue#78TylerHanavan2025-03-29 17:43all output from shell actions is written to the test results file twice
- Issue#77TylerHanavan2025-03-29 15:19retest commit button should also delete lock file
- Issue#71TylerHanavan2025-03-29 14:43Tests which are failing are not marked as failing in the test results
- Issue#76TylerHanavan2025-03-28 11:41tests with fatal errors are not being written into test results & commits table again
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.