CDcdnsteve·Oct 2, 2015
They are looking for Rails apps to run TTNT tests on to see if your tests pass the test... ;)
https://github.com/Genki-S/ttnt/issues/38
In TTNT: Test This, Not ThatGenki-S
ttnt
Ruby2015–2015
Genki-S / ttnt
ttnt
Test This, Not That! (Google Summer of Code 2015 project under Ruby on Rails)
3Distinct people
4Mentions
0Explicit recommenders
263GitHub stars
What to know before exploring
What it is
Test This, Not That! (Google Summer of Code 2015 project under Ruby on Rails)
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week4 dated mentions
Observed mentions: 2015-08-07 23:54:30 UTC to 2015-10-02 13:53:24 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Aug 3 | 2015-08-03 00:00:00 UTC | 2015-08-10 00:00:00 UTC | 1 | 0 | 1 |
| Aug 10 | 2015-08-10 00:00:00 UTC | 2015-08-17 00:00:00 UTC | 0 | 0 | 0 |
| Aug 17 | 2015-08-17 00:00:00 UTC | 2015-08-24 00:00:00 UTC | 0 | 0 | 0 |
| Aug 24 | 2015-08-24 00:00:00 UTC | 2015-08-31 00:00:00 UTC | 0 | 0 | 0 |
| Aug 31 | 2015-08-31 00:00:00 UTC | 2015-09-07 00:00:00 UTC | 0 | 0 | 0 |
| Sep 7 | 2015-09-07 00:00:00 UTC | 2015-09-14 00:00:00 UTC | 0 | 0 | 0 |
| Sep 14 | 2015-09-14 00:00:00 UTC | 2015-09-21 00:00:00 UTC | 0 | 0 | 0 |
| Sep 21 | 2015-09-21 00:00:00 UTC | 2015-09-28 00:00:00 UTC | 0 | 0 | 0 |
| Sep 28 | 2015-09-28 00:00:00 UTC | 2015-10-05 00:00:00 UTC | 3 | 2 | 1 |
What Hacker News says
4 sourcesWell, it is kind-of possible for Ruby/Rails. I half-built such a system once. Here's what you do:
* Gather coverage information when running tests or compiling assets.
* Use that to generate Rakefiles for running tests / compiling assets that have dependencies on the source files they would touch.
* Run the tests once, recording information about the git status of each dependency.
* When the git status of a file changes (i.e. you've just fetched some changes), mark the dependency as dirty
Even better, it you're gathering coverage data and know the test status for each commit, then not only can you show the commit that broke the build, you can show the particular part of the diff that broke the build.
Here's a guy who was trying to do some of this: https://github.com/Genki-S/ttnt
In Things I would build if I worked at GitHub