«« Next » « Previous
«« Next » « Previous

Link Details

Previous | Next

Surprise Me!
We're glad you're here, but we'd be thrilled if you voted! Login and vote now.
Link 79895 thumbnail

By bloid
via freelancemadscience.blogspot.com
Submitted: May 08 2008 / 05:12

The problem with JUnit
Object oriented design is based on the idea of encapsulating behavior. Testing is an attempt to reveal and examine behavior. You can't have both.
Vote up
Vote down
  • 1
  • 2
  • 188
  • 32
SaveShareSend Tags: ,

Comments

Add your comment
User 102928 avatar

dglasser replied ago:

0 votes Vote down Vote up Reply

Voted down because of the statement "Testing is an attempt to reveal and examine behavior." This guy desperately needs a clue.

User 172008 avatar

Daniel Dyer replied ago:

0 votes Vote down Vote up Reply

Agreed. Avoid reflection in your tests - test the OBSERVABLE behaviour and state.

Not only that, but making this a static typing vs. dynamic typing argument is a bit of a stretch. This seems to be more about preferring Ruby's reflection to Java's. Despite the title, I didn't see any mention of a specific problem with JUnit.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (1)



Voters Against This Link (2)