Following is an overview of the characteristics of test cases as they relate to
.NET Explorer:
- Each test scenario includes an
Init test case and an
End test case. Multiple
Main test cases may also be defined. An
Init test case is the first test case that is called during a test run.
Init test cases often include method calls that are related to initialization, logging in, or start-up. An
End test case is the last test case that is called during a test run.
End test cases often include method calls that are related to clean-up, for example logging off.
- Main test cases are executed between
Init and
End test cases and may include any sort of method call.
- A local variable is only valid within a single test case and cannot be passed to another test case. Only global variables
can be used to pass values between test cases.
- Each test case must have a unique name.
- Test case properties can be edited by selecting a test case in the
Test Scenario menu tree and defining field values in the
Output Data Properties field:
- StopAtError is the attribute that defines the number of errors that can occur during an animated run. If this number is reached, the
animated run aborts. Setting this attribute to
0 specifies that errors will be ignored.
- CallCount is the attribute that defines the number of times that a test case will be called during an animated run.
- You can create, copy, and remove test cases by right-clicking a test case in the
Test Scenario menu tree and selecting the respective menu item.