Rename back to InvokeAction()

[cottsak]

The 5a0aa8b means that a test might only have one controller call which is fairly limiting.

The set up of a test may need to get some result from a different controller call and therefore InvokeAction() instead of ActAction() seem more appropriate. Tests like this (multiple controller calls) are more complete in terms of real user interaction anyway so should be encouraged not discouraged.

[cottsak]

Maybe you should only be having one SUT per test? Maybe the controller call in the "set up" or Act part of the test is not the best way to set up the state for the second controller call which is actually the SUT? Maybe you can set up the same state with Session and achieve the same result?