tag:blogger.com,1999:blog-10846234.post111177575982713327..comments2023-06-22T09:51:55.639+01:00Comments on BOBABLOG: Agile software development and Salesforce: Assertive DocumentationRob Bailliehttp://www.blogger.com/profile/06513796097645814224noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-10846234.post-1112716167340385732005-04-05T16:49:00.000+01:002005-04-05T16:49:00.000+01:00Another way you can capture the intent of the test...Another way you can capture the intent of the testcase without resorting to comments is to use a tool such as <A HREF="http://agiledox.sourceforge.net/" REL="nofollow">TestDox</A>.<BR/><BR/>It generates human-readable text from the method names in your testcase, so if you believe to the <I>one assert per method</I> idea then you can express the intent of the method by naming it suitably.<BR/><BR/>Joe Walnes shows a way to do something similar by <A HREF="http://joe.truemesh.com/blog/000175.html" REL="nofollow">overridding the getName() method</A> of the TestCase.Andrew Beacockhttps://www.blogger.com/profile/01039992884679308726noreply@blogger.com