News for hackers. Stuff that matters.
Re:Questions to ask yourself when writing tests by amarkov on Tuesday January 02, 2018 @06:35AM (#16051294)
All the projects I've most enjoyed working on had clear, explicit test failures, which almost always gave me enough information to hunt down what I'd broken and where. Obviously that's not realistic for some kinds of projects. But even in a legacy C project, if I had to pull out stack traces and profilers and GDB every single time I wanted to understand why a test failed, I would say I'm working in a pretty terrible codebase.

There are no comments on this comment yet.