Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 7
    ...and btw, I'm up to my neck in guilt right now. Commented May 3, 2012 at 16:38
  • 2
    you don't have time to unit test - huge BS. So, no time to unit test, but there is always time to fix bugs. Commented May 3, 2012 at 19:38
  • tru, @VJovic. But if the OP doesn't really feel the NEED to test, because not testing still hasn't burned him, and just does things out of blind faith. Well, then I think that would be even worse, as getting the abit of doing things out of blind faith gets you into very strange corners. Commented May 3, 2012 at 20:23
  • 1
    Actually, my reason for not unit testing isn't lack of time - it's usually either I don't know what the code will do well enough to spec it out, or I don't know the technologies well enough, so that learning and deploying a testing framework would be an additional burden. Commented May 4, 2012 at 8:06
  • Coding to requirements is key in TDD. You should have some sort of document telling you what the code should do in a particular situation (this could be as simple as "when I click this button I expect to go to page X", as PD as GAAP rules for accounting, and as generic as "we need a system that will take in these files and produce this output; go do it"). If your requirements in a particular area aren't granular enough to write a unit test that mirrors them, then you have to interpolate based on what you do know. If you can't do even that then you need more requirements. Commented May 7, 2012 at 16:08