The Artima Developer Community
Sponsored Link

Weblogs Forum
A Set of Unit Testing Rules

50 replies on 51 pages. Most recent reply: Jan 21, 2011 2:19 AM by Steve Merrick

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 50 replies on 51 pages [ « | 1 ... 28 29 30 31 32 33 34 35 36 ... 51  | » ]
Matt Gerrans

Posts: 1153
Nickname: matt
Registered: Feb, 2002

Re: A Set of Unit Testing Rules Posted: Sep 14, 2005 8:39 PM
Reply to this message Reply
> Teams can create whatever rules they want or name things whatever
> way they wish to.

I'm not sure I agree with this. Communication across teams and the industry is important too. Why muddy the waters by everybody defining things as they like? The whole idea of design patterns is to apply a shared vocabulary to common patterns in code. Maybe unit tests are just a design pattern...

I think you should stick to your strict definition, but I think these other kinds of tests need a good name. What if you are developing an OS, a database, etc.? You need to have plenty of tests, whether you call them unit or something else. How would you do TTD development on these things if you were limited to unit tests? Or is TDD not limited to unit tests?

Flat View: This topic has 50 replies on 51 pages [ « | 28  29  30  31  32  33  34  35  36 | » ]
Topic: Computer About to Play Jeopardy Previous Topic   Next Topic Topic: The Search for Requirements

Sponsored Links


Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use