wood burning stoves*
The moose likes IDEs, Version Control and other tools and the fly likes Eclipse 3.2 and JUnit Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "Eclipse 3.2 and JUnit" Watch "Eclipse 3.2 and JUnit" New topic
Author

Eclipse 3.2 and JUnit

Haakon Lind
Greenhorn

Joined: Sep 18, 2002
Posts: 22
Hi, I`m migrating from Eclipse 3.1 to 3.2 and stumbled upon a strange problem with the integrated JUnit. In 3.2 I can`t get the "Compare Actual With Expected Test Result" to be enabled, where it is in 3.1 on the same test.

Is this feature not implemented in 3.2 or am I missing some configuration?

Thanks,
Haakon
Haakon Lind
Greenhorn

Joined: Sep 18, 2002
Posts: 22
Ok, this worked with an update, please delete.
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 30377
    
150

Haakon,
We like to leave threads with answers. That way if someone has the same problem, they will know the solution.

Good to hear you got it working!


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Stefan Wagner
Ranch Hand

Joined: Jun 02, 2003
Posts: 1923

I get the same problem on Eclipse Juno (4.2):


Most answers I found report that this is the case if your assertion doesn't compare Strings, but my article.author is a String. Unfortunately it is null, and if it isn't, the comparison works as expected.


http://home.arcor.de/hirnstrom/bewerbung
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Eclipse 3.2 and JUnit