• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Junit inn Action: JUnit clash in Eclipse?

 
Ranch Hand
Posts: 218
VI Editor Ruby Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When using JUnit inside Eclipse, often times I got unresolved method
for assertFalse(). Do you have any idea why? In the beginning I thought there was a clash in JUnit.jar version that shipped with Eclipse. Especially now that JUnit use assertTrue and assertFalse to circumvent 1.4's assert.
But funny thing is assertTrue has no problem, I would have thought JUnit will have
both assertTrue and assertFalse in the same version.
FYI, I was using Eclipse 2.1 for my project.
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Assert#assertFalse(...) was added in JUnit version 3.8. Assert#assertTrue(...) was already there before 3.8.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic