A modern, fast and flexible .NET testing framework
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 94%
Response Time: -
First Timer Success: 100%
thomhurst/TUnit has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in thomhurst/TUnit respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 71.8 places thomhurst/TUnit in the S tier.
The external contributor pull request merge rate for thomhurst/TUnit is 94.3%, based on public PR activity from non-core contributors.
thomhurst/TUnit currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in thomhurst/TUnit. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/thomhurst/TUnit?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (42% approval). Keep your diff compact for rapid review.
Problem Statement Hi! The docs (e.g. Troubleshooting) state that "test methods must be public instance methods". Is there any appetite for relaxing this? I actually only care about this in the reflective test data collector and I'm asking because of F#, where in other testing frameworks such as NUnit it's pretty idiomatic to define e.g.: module MyTests = [<Test>] let foo () = if 3 <> 4 then failwith "oh no" This module compiles to an abstract sealed class. TUnit's reflective mode skips types which are Type.IsAbstract. Proposed Solution Permit this test, which is just a static rephrasing of https://github.com/thomhurst/TUnit/pull/2250/files#diff-7c60e0e872421ee5ed36abe6e6c58fd1565ae591e4088261372ebeeb4fb34cb2: open TUnit.Core module Tests = [<Test>] let test () = printfn "Test method executed" In the case that all the collected test methods are static, I think it's safe to relax the IsAbstract skip from the collector (though I'm not deeply familiar with
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to thomhurst/TUnit, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of thomhurst/TUnit acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 94.3% were successfully merged into the primary branch.
thomhurst/TUnit has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 71.8 places thomhurst/TUnit in the Elite tier.
The external pull request merge rate is 94.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, thomhurst/TUnit currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for thomhurst/TUnit are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.