Just curious...is there a compelling reason why BaseControllerTest is presented as an abstract class with protected PrepareController methods?
I ask because if I have test classes that are derived from another base class I can't easily use the BaseControllerTest. If I make *my* base class derive from BaseControllerTest then I have to re-expose all the PrepareController methods so that they're accessible from my final class...which is a pain. What's more, if I want to access other protected items like the EngineContext I have to do more work. Why not instead have a concrete class called MonoRailTestHelper with the main functionality presented (eg. PrepareController, Context, etc.) as public? Then one could simply create an instance of the helper to use in a test, prepare a controller using the helper and then use the helper to access related contextual information set up when the controller was prepared. Thoughts? Cheers, Symon. Symon Rottem http://blog.symbiotic-development.com -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
