Comments on: Unit testing interface implementations

By: Contract Tests with TestNG: update

Contract Tests with TestNG: update — Fri, 22 Aug 2008 23:00:01 +0000

[...] functionality of abstract classes works properly in all concrete subclasses. Certainly this has been mentioned before, generally under the name Abstract Tests or Contract Tests. Also, the idea seems [...]

By: Ilya Bobir

Ilya Bobir — Sat, 15 Dec 2007 07:31:51 +0000

It constantly gives me an error. Please check the server logs. =)

By: Ilya Bobir

Ilya Bobir — Sat, 15 Dec 2007 07:30:11 +0000

For some reason I can not submit the rest of my post

By: Ilya Bobir

Ilya Bobir — Sat, 15 Dec 2007 07:26:48 +0000

Suites can be connected to form a tree. A suite for the interface contract can be added as a child to the suite that tests the class.

About telling which implementation of the interface to test, it is quite easy with JUint 3 where you are creating suites yourself. You can just add a method to the suite that will take an implementation factory and will propagate it into all contained tests. Then you need to do a call to supply the factory in addition to attaching the interface test suite as a child to your class test suite.

By: Paul

Paul — Wed, 12 Dec 2007 20:14:00 +0000

I can’t comment on how well this works in practice as since I wrote the post I’ve been working solely with Ruby.

In the past I’ve alway tried to avoid suites as test cases inevitable accidentally get left out however in this case either way you’d have to remember to add an entry to something, either the suite or the interface testcase.

As I’ve not used suites much I’m not sure how go about telling the generic test which implementation of the interface to test, or I may have misunderstood what you meant.

One other small benefit that has just come to mind of having all the implementations of an interface listed in the test for the interface is that if you change the interface you just need to run the test for it to discover which classes are broken rather than having to remove all compiled class files and compiling everything to pick up which classes were dependent on the interface.

By: Ilya Bobir

Ilya Bobir — Wed, 12 Dec 2007 01:27:40 +0000

Don’t you think that enumerating all the interface implementations in the interface test is a bit wrong?
It seems to me it would be more correct to have some kind of a generic test suite that tests the interface contract and use it as a part of a test suite for each implementation.

By: Screened Twenty

Screened Twenty — Tue, 22 May 2007 00:22:37 +0000

Hello

We’ve got a non-profit site here with an article on Unit Testing in general, located at: http://coderslog.com/Unit_Testing_101

Hoping to get examples on there soon. The site itself is a journal of common code/configurations and other hard to find information. Should come in handy for building high performance large scale java applications and such.