3.2.1.3 Omit Exceptions Exceptions are used in the individual test steps. Exceptions are protection mechanisms. An exception is an event, that when it occurs, causes the test run to automatically abort. For example, if you were performing a break test, you might want to include an exception based on distance. When the distance = x, stop the test because the break should have occurred before this distance was achieved. When an exception occurs, the test is aborted. No results are calculated and the run is identified in Red as an invalid test. When Omit Exceptions = YES, we omit all data for the invalid test- no data is saved. In some situations, it may be desirable to save the data for a test that was ended due to an exception. In these situations, the Omit Exceptions function is used and the option is changed to NO. When Omit Exceptions = NO, we do not omit the data. Rather, we save the data until the test was aborted. NOTE Data is saved when the Export Raw option is Yes. If this option is No, no data is exported.
When Omit Exceptions = YES (default), no data is saved for the aborted test run.
L2 Plus Test Builder - Pre Test Omit Exception When YES, no data is collected for this run
L2 Plus Test Builder - Exception An Exception is used to denote when to terminate a test
Selecting the STOP IF function presents you with options for terminating a test. In the example, the break step will terminate if the Distance Limit of 100mm or the Load Limit of 45N are achieved before the sample breaks.
When Omit Exceptions = NO and the Export Raw and Export Results are enabled in Post Test, if an event occurs that causes the test run to terminate, the data is collected for the run from the start up to the exception event.
L2 Plus Test Builder - Pre Test Omit Exception When NO, data and results may be available up to when the event occurred
8
Made with FlippingBook - professional solution for displaying marketing and sales documents online