Talk:Unit testing: Difference between revisions
imported>Ed Poor ({{CZ:The Article Checklist}}) |
imported>Howard C. Berkowitz (Agile methodology) |
||
| (13 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{subpages}} | ||
I got 8 red links. Should I start writing those articles, or maybe just unlink my red links? --[[User:Ed Poor|Ed Poor]] 13:37, 10 May 2007 (CDT) | |||
Definitely start writing those articles! --[[User:D. Matt Innis|Matt Innis]] [[User talk:D. 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: | |||
#saves time | |||
#delivers more bang for the buck | |||
#is more satisfying to the end user | |||
How can I write about this? --[[User:Ed Poor|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. | |||
[[User:Howard C. Berkowitz|Howard C. Berkowitz]] 00:43, 16 April 2011 (UTC) | |||
Latest revision as of 18:43, 15 April 2011
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:
- saves time
- delivers more bang for the buck
- 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)