Handling Test Completion

Why stop at classifying tests as pass or fail? TestMap Extensions functions also allow you to track 'soft' errors without stopping your test, to flag test script errors as 'bugs', and to shut down your test bed when a system error is encountered.

Give your test scripts the power to:

	classify test exceptions as they occur (soft errors, errors, test script bugs, system errors)
	behave appropriately for each type of test completion
	save all test completion results to a database or comma delimited ASCII file
	define what information is captured at the end of each test
	automatically re-run failing tests when intermittent errors are suspected
	collect agent trace information only for failing tests that are re-run

Functions for Classifying and Ending Test Case Execution

TmExitError: for those errors that need analysis for further classification
TmExitBug: for those errors that you know are test script problems
TmExitSoftError: for those errors that are not severe enough to stop execution - tracks the error but continues the test case.
TmExitSystemError: for those errors that need to halt all test bed execution - even in a distributed environment with multiple host machines.
TmExitNA: for those test cases that are not applicable in the current environment
TmExitInc: for those test cases that are inconclusive

Function for Classifying 4Test Exceptions

TmExceptClassify: Converts regular 4Test exceptions into classified errors. This highlights test script errors with a "Bug" prefix in the results file if the error is a run-time syntax error. This function is called as part of the standard TestMap Extensions test case exit processing.