I just refactored the Agatha RequestProcessorTest.ExceptionHandling AcidTest to take advantage of the new QuickNet features and it is throwing a failure.
This might be a bug in QuickNet.
This might be an erroneous spec definition.
This might be a bug in Agatha.
I’m hoping for the latter
.
I added the new features in order to deal with problems I face in a production environment.
Agatha, however, is a totally different thing. We’re testing a framework/lib, not an app.
Apart from the fact that definitely something is going wrong somewhere, this test clearly exposes some weaknesses of the newly implemented features.
F.i. :
– Shrinking does not seem to produce the minimal fail case.
– Reporting is too confusing.
I will have to fix this first in order to be able to determine whether the bug is in QuickNet, in Agatha, or in the spec definition.
And that, my friends, gets me all excited.