Like is suggested in #6, some tests may need to invoke more than one controller action. If this is true it's likely those two or more actions are not from the same controller. As it is currently designed, this infrastructure does not support that scenario. Perhaps it makes sense to allow the InvokeAction() method to specify a generic argument for any controller thus giving th test a lot more flexibility?
Like is suggested in #6, some tests may need to invoke more than one controller action. If this is true it's likely those two or more actions are not from the same controller. As it is currently designed, this infrastructure does not support that scenario. Perhaps it makes sense to allow the
InvokeAction()method to specify a generic argument for any controller thus giving th test a lot more flexibility?