Sounds like you are using EasyMock in an integration test. If you look at the HiveMind test suite, you'll see a difference between true unit tests (using EasyMock), and integration tests (that typically parse and build a Registry and then check behavior on it).
The integration tests use traditional mock object implementations ... the roll by hand kind. On Tue, 28 Sep 2004 11:35:37 +0200, Meyer Harald <[EMAIL PROTECTED]> wrote: > Hello, > > I have got a problem with using HiveMind and EasyMock. As I understand it, it > is not really a HiveMind issue. Maybe you have got an idea, how this can be > solved: > > I have a service for which I use set-object to set a property. set-object > uses the service-property of another service. This other service is mocked > using Easymock, without delivering an implementation for the getter of the > property. The test case should now fail with an AssertionFailedError. But > instead it passes. > > The problem is, that the AssertionFailedError gets subsequentially wrapped by > an InvocationTargetException and an ApplicationRuntimeException. This > run-time exception is then caught in > org.apache.hivemind.schema.rules.ReadAttributeRule(), which logs the error > and continues. > > Thanks > Harald Meyer > > . > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
