Talk:Unit testing

From Citizendium
Revision as of 18:43, 15 April 2011 by imported>Howard C. Berkowitz (Agile methodology)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
This article is developing and not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
To learn how to update the categories for this article, see here. To update categories, edit the metadata template.
 Definition Method of automatically testing software that is designed to check each unit. [d] [e]
Checklist and Archives
 Workgroup category Computers [Categories OK]
 Talk Archive none  English language variant British English

I got 8 red links. Should I start writing those articles, or maybe just unlink my red links? --Ed Poor 13:37, 10 May 2007 (CDT)

Definitely start writing those articles! --Matt Innis (Talk) 14:02, 10 May 2007 (CDT)

Sorry, it's been almost 4 years. I've done a lot of unit testing, but I haven't gotten around to writing about it.

The weakness of the article is that it doesn't say much about choosing what to test (i.e., making test cases), the relationship to refactoring, or the influence of the testing-refactoring cycle on design. The whole idea of test-driven development (TDD) is that one can forego the old idea of Big Design Up Front in favor of a more agile approach that:

  1. saves time
  2. delivers more bang for the buck
  3. is more satisfying to the end user

How can I write about this? --Ed Poor 22:02, 14 April 2011 (UTC)

Compare and contrast Agile software development, Waterfall software development (or BDUF), etc. ? There's a good Agile Methodology mailing list.
Maybe at least some lemmas -- or more -- on use cases and the like.

Howard C. Berkowitz 00:43, 16 April 2011 (UTC)