tag:blogger.com,1999:blog-7594548881489150326.post5375097812470320385..comments2014-03-14T16:35:24.297-04:00Comments on zdsbs: Testing Interface ImplementationsZachary D. Shawhttp://www.blogger.com/profile/11739142419934264380noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7594548881489150326.post-17581015141582419892008-11-14T16:55:00.000-05:002008-11-14T16:55:00.000-05:00it's possible there are some Junit wrinkles I don'...it's possible there are some Junit wrinkles I don't know about, but if you have:<BR/><BR/>public class BarTest extends FooTest<BR/><BR/>and run BarTest in Junit, you'll execute and tests in FooTest as wellZachary D. Shawhttps://www.blogger.com/profile/11739142419934264380noreply@blogger.comtag:blogger.com,1999:blog-7594548881489150326.post-61208912330249445332008-11-14T16:07:00.000-05:002008-11-14T16:07:00.000-05:00Excellent stuff. I certainly love the "DRY"ness o...Excellent stuff. I certainly love the "DRY"ness of it. As long as JUnit supports running tests in the super class using the implementation you assign (do you do this in the constructor or something?) in the subclass, I see nothing wrong with it. In fact, I can think of nothing better than what you've done. Damn you for making me say that.ekerwinhttps://www.blogger.com/profile/04750159243098329344noreply@blogger.com