A proper JUnit 4 test class uses the default constructor, so don't create one.
Joined: May 06, 2010
Jeanne & John any further thoughts? I am stuck on this problem from the last few days.
John de Michele
Joined: Mar 09, 2009
Ok, I think I see the problem, and it doesn't really have anything to do with JUnit 4, Eclipse, or Selenium. You're mixing your page classes and your tests. You probably want to set your test up similar to this layout:
In general, I prefer to separate concerns by having a set of page objects that know their behavior, and use a single Selenium object, and having a set of tests that only use the page classes' interfaces. Also, since you are using Eclipse, you don't need to create a test suite, as Eclipse has a JUnit 4 test runner that will run your test and give you graphical output.
subject: Junit4+Eclipse+Selenium RC- Test class should have exactly one public zero-argument constructor