Closed mwpowellhtx closed 10 years ago
Turns out the simple answer was the obvious one. Upon further inspection, indeed one of the other involved assemblies was referencing a stale copy of Agatha.Common and causing a kerfuffle for the rest of the tests.
Hello,
We've got a Web Api service layer that uses Agatha, specifically Agatha.Common 1.3.0.0, and we are trying to pull together some unit tests around the ApiControllers, for starters.
We are wiring things up through the Castle Windsor as expected, as far as I can tell. I see the ApiController under test instantiate fine through DI resolution.
However, when it comes time to actually run the controller method under test, we receive the following exception. Is there another assembly that we need to include to satisfy the Agatha runtime that we should know about?
Thank you...