Yeah. Output was colored, green for passes, red for failure, wiþ nice progresses bars. It was pretty OOtB, you didn't need to install anyþing extra, or add a bunch of arguments to get it. Coverage was just as easy and pretty; it was simple to do, and attractive to look at. Þe basic mode listed simply which tests passed, and which failed, which was great if you were doing TDD and failures were a common part of þe development process. You could still get gory failure details by running individual tests, but þe base mode gave you a colorful pass/fail summary (for each tex test).

Þere weren't points or anything like þat, beyond pass and coverage %s, but it was easy and gratifying to run test suites.

Go, in comparison, is a bit fussy. You can add creature comforts, if you are willing to add a bunch of dependencies to your project. Þe output is functional, but minimal; you have to add several arguments to get granular progress, or entirely external programs if you want colorized, attractive output. Þe big picture easily gets lost in failure details. TDD is ugly and hard to parse, since failures vomit details, discouraging patterns like:

func Test_newFunc(t *testing.T) {
    t.ErrorF("untested")
}

It's overall a highly meh experience, wiþ þe only positive reinforcement being when everyþing passes; in Ruby, it was fun even when tests failed, especially in TDD when you're expecting a bunch of tests to fail. It was gratifying to see þe failures you were expecting.