AfterTestActionCommand

 BeforeTestActionCommand

 CancelAfterCommand

 ConstructFixtureCommand

 DisposeFixtureCommand

 EmptyTestCommand

 FixturePerTestCaseCommand

 MaxTimeCommand

 OneTimeSetUpCommand

 OneTimeTearDownCommand

 SetUpTearDownCommand

 SetUpTearDownItem

 SkipCommand TODO: Documentation needed for class

 TestActionCommand TestActionCommand handles a single ITestAction applied to a test. It runs the BeforeTest method, then runs the test and finally runs the AfterTest method.

 TestActionItem TestActionItem wraps a single execution of an ITestAction. Its primary purpose is to track whether the BeforeTest method has been called and suppress calling the AfterTest method if it has not. This is necessary when ITestActions are used before and after a CompositeWorkItem, since the OneTimeSetUpCommand and OneTimeTearDownCommand are separate command chains. By sharing a TestActionItem between the setup and teardown chains, the two calls can be coordinated.

 TestMethodCommand TestMethodCommand is the lowest level concrete command used to run actual test cases.

 TheoryResultCommand TheoryResultCommand adjusts the result of a Theory so that it fails if all the results were inconclusive.

 TimeoutCommand creates a timer in order to cancel a test if it exceeds a specified time and adjusts the test result if it did time out.

 AfterTestCommand AfterCommand is a DelegatingTestCommand that performs some specific action after the inner command is run.

 BeforeAndAfterTestCommand TestActionCommand handles a single ITestAction applied to a test. It runs the BeforeTest method, then runs the test and finally runs the AfterTest method.

 BeforeTestCommand BeforeTestCommand is a DelegatingTestCommand that performs some specific action before the inner command is run.

 DelegatingTestCommand DelegatingTestCommand wraps an inner TestCommand. Derived classes may do what they like before or after running the inner command.

 TestCommand TestCommand is the abstract base class for all test commands in the framework. A TestCommand represents a single stage in the execution of a test, e.g.: SetUp/TearDown, checking for Timeout, verifying the returned result from a method, etc. TestCommands may decorate other test commands so that the execution of a lower-level command is nested within that of a higher level command. All nested commands are executed synchronously, as a single unit. Scheduling test execution on separate threads is handled at a higher level, using the task dispatcher.