tag:blogger.com,1999:blog-7594548881489150326.post3276511253203667407..comments2014-03-14T16:35:24.297-04:00Comments on zdsbs: Contract TestsZachary D. Shawhttp://www.blogger.com/profile/11739142419934264380noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7594548881489150326.post-33161678955385757732009-09-22T22:02:29.190-04:002009-09-22T22:02:29.190-04:00oh yeah, I forgot we upgraded from XXXBase to Abst...oh yeah, I forgot we upgraded from XXXBase to AbstractXXXFixture. But XXXContract I think is perfectly fine. The word fixture never sat well with me because a test fixture refers to the state needed to run tests not the tests themselves.<br /><br />and of course... I agree the test task should change. And I really like the use of the word contract. An abstract test class is really talking about a contract you must fulfill. If you'd like to be sure you're implementing everything correctly. <br /><br />It being an Abstract Class is just an implementation detail. So, I still think they should be called XXXContractZachary D. Shawhttps://www.blogger.com/profile/11739142419934264380noreply@blogger.comtag:blogger.com,1999:blog-7594548881489150326.post-42706601750859083282009-09-22T18:57:16.864-04:002009-09-22T18:57:16.864-04:00Well, we had also been using AbstractXXXFixture......Well, we had also been using AbstractXXXFixture... but in reality the test task needs to change...Ashhttps://www.blogger.com/profile/01844686398403027089noreply@blogger.com