Hello -

I've recently joined a team that has created quite a few unit tests over their source code. They are run as part of our ant/cruise-control based continuous build and run successfully. This is good!

However, when I try to run them within Eclipse by right-clicking on my project name, and selecting 'run as->junit test' (which I believe will find all junit tests in the project and run them in some order I can't discern), I get many jUnit Errors, all of the format:

org.hibernate.MappingException: Unknown entity: package.name.class.name (where my specific details are obviously here)

The specific class varies depending on the test.

However, when I attempt to execute any of the failed tests individually they work.

I assume this must be an ordering problem, or an issue with configuring hibernate multiple times (each test class typically does a configure in its setup method).

I'd really appreciate any pointers. I'm not sure anyone else in the team has tried this!

Thank you
Mike

Some more info on this:

- looks like when we execute our unit tests via the Ant task, we have 'fork' set to 'yes'; this implies each test class gets it's own clean jvm
- in eclipse, all tests you choose to execute together get a single jvm
- in each of our jUnit setUp methods, we configure Hibernate, but with different hbm files

So, I'm wondering if the subsequent calls to configure (within the same jvm) are just being ignored. I don't see any warnings to this effect in the logs, but I am getting the mapping exception when we attempt to call 'save'.

Mike