Comments on: JUnit recipes: Work around static attributes in classes

By: himanshu

himanshu — Fri, 30 Nov 2007 12:50:52 +0000

Thnks for your comment.
I have to work around with Legacy Code a lot. Client usually do not allow us to change the design. So sometime I have to use stubbed classes or jMockit.

By: stephan

stephan — Wed, 03 Oct 2007 16:34:33 +0000

Thinking about that again, as Qrilka said, the problem (in this case) arises from interfaces depending on classes. So interfaces should only depend on other interfaces, not on concrete classes.

By: stephan

stephan — Sun, 26 Aug 2007 09:55:39 +0000

@Qrilka: Yes you’re right. I most often use interfaces instead of classes, but this was legacy code which couldn’t easily be changed.

But although most people would use interfaces for services (storage, view), I seldom see people using interfaces for business objects like Person.

By: Qrilka

Qrilka — Sun, 26 Aug 2007 09:12:20 +0000

I think the problem is in using concrete classes not interfaces. So If Person would be just an interface you won’t have such situation. Concrete classes enlarge code coherence and create problems like the one you’ve mentioned.

By: stephan

stephan — Fri, 24 Aug 2007 16:49:04 +0000

@Thomas: The names have been changed to protect the innocent :-)

But as a side node, I’ve been moving further and further away from OO to a data holder object and service programming style. Any business logik inside of objects looks now suspicious to me. I think services like AgeCalculator are much more versatile and exchangable.

By: Thomas Hawk

Thomas Hawk — Fri, 24 Aug 2007 16:28:15 +0000

I am curious as to why you need an AgeCalculator class with a calculateAge method. I, of course, am not familiar with your code, but it seems to me calculateAge should be a method in the Person class.

By: The Disco Blog » Blog Archive » The weekly bag– August 24

The Disco Blog » Blog Archive » The weekly bag– August 24 — Fri, 24 Aug 2007 14:55:10 +0000

[...] JUnit recipes: Work around static attributes in classes- Some hip advice here. [...]