tag:blogger.com,1999:blog-6278117270415743822.post251677155640500470..comments2022-06-11T06:19:53.837-07:00Comments on Exploring Agile Solutions: Test-Driven Design/DevelopmentC. Keith Rayhttp://www.blogger.com/profile/06981113185117230625noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6278117270415743822.post-59062984822031436482013-05-16T12:08:42.822-07:002013-05-16T12:08:42.822-07:00Bad phrasing on my part.
Repeat until you can'...Bad phrasing on my part.<br /><br />Repeat until you can't think of NEW tests. Emphasis on "NEW".<br /><br />Not useless variations of existing tests. Not tests that pass when you first run them because the code already exists. Not tests that don't actually test your code.<br /><br />Tests that are relevant to the feature you are testing; tests that exercise some logic you haven't written yet. If you can't think of a _new_, _relevant_, test, then you are finished.<br /><br />Combine this with other XP practices, such as "StoryTest Driven Development" aka "Acceptance-Test Driven Development" aka "Behavior Driven Development" to insure that you only write the minimum code and tests for a new feature to work, and also refactoring to maintain a good design.<br />C. Keith Rayhttps://www.blogger.com/profile/06981113185117230625noreply@blogger.comtag:blogger.com,1999:blog-6278117270415743822.post-1082005252731284322013-05-14T00:53:25.673-07:002013-05-14T00:53:25.673-07:00"Repeat until you can't think of any new ..."Repeat until you can't think of any new tests." Did he really write that? You should be doing exactly the reverse: Writing the fewest number of tests that enable you to accomplish your goal, whether it's writing new code or testing existing code. Why would you ever want to write more than the minimum test needed to reach your goal? Unknownhttps://www.blogger.com/profile/04788608914849681144noreply@blogger.com