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.

Required fields*

3
  • 17
    "Pull down some sweet, low hanging fruit, and you will be able to sell the process.": I think they got to this stage already (they saw potential advantages in using unit tests) and this is why they were convinced to give it a try. The problem is rather how to scale the low hanging fruits to doing unit testing systematically. The only project I worked on in which unit tests were used systematically had more unit test code than actual product code. If a team is not prepared to spend more time coding unit tests than actual application code, then IMO the approach will probably not work. Commented Feb 4, 2013 at 13:01
  • 4
    That is more of a management issue. Is the code considered "done" before it is documented? Before it is checked in? Before it includes and passes unit tests? How you approach this really depends on your role. Are you a peer? If so, show others how it makes your code easier for them to reuse and maintain. Are you a lead? Pick your programmer who has the most code problems and help them add tests to avoid those problems. Are you a boss? Set it as a standard that "the code isn't done until the unit tests are in and passing. Commented Feb 4, 2013 at 14:00
  • 1
    @SkipHuffman your comment should be added as an edit to current answer. Commented Feb 4, 2013 at 14:02