Event Log |

The Event Log tab displays the recent errors and status messages that have occurred during a test run. It is possible to save a copy of the test events using the Copy to clipboard functions, the ‘File -> Save Report’ menu item, or in a test report using 'Preferences->Logging'. The event window is updated in as events occur and can be left open while a test run is in progress. There is no practical limit to the number of events that can be written to a test report. Context sensitive popup menus are available using the mouse 'Right click', while double clicking on an event will open the "Common test error messages" help to display a description common errors. Event Classification Test events (such as test errors) are classified into different severity levels of CRITICAL, SERIOUS, WARNING or INFORMATION. Where an informational line (related to this error) follows the error line, the error classification is not repeated and is shown as a LOG NOTE (to aid determination of the number of unique errors per classification). A test failure is defined to be one or more CRITICAL, SERIOUS or WARNING errors. INFORMATION level events are logged for information only and are not considered to constitute a test failure. An event classification of NONE also exists and this means that the event is not meaningful in the context of the test being undertaken and events configured this way are ignored. All events may be configured to not be reported if they are not meaningful in a specific test environment (by setting to NONE in BITErrorClassifications.txt). Each line is color coded based on the Error Classification. Time stamp The time stamp records the time when the event occurred. The format is, YYYY-MM-DD HH:MM:SS Test type The test type refers to the name of the test which originated the event. Examples are, “RAM”, Floppy Disk”. The word “Status”, indicated that the event is not an error but just a status message. Details This is a text field that contains additional information about the error (or status message). In some cases a log entry may be spread across two lines. The 1st line will contain some general information about the error and the 2nd line will contain more detail. Some error messages may contain internal program variables (and thus be fair cryptic). These are not always intended to be interpreted by the user can but help us track down faults in our software. Configuring Error Classifications Each of the standard errors detected by BurnInTest can configured to include a customer specific string and error classification. The file BITErrorClassification.txt (in the software directory) contains the error text and classification used by BurnInTest. The file is formatted as a Comma Separated File with four fields:
1. | Error number – this must not be changed by the customer;
2. | Error description text – this may be changed. This must be a sting enclosed by quotes;
3. | Error classification – this may be changed. This must be one of the following text values (not in quotes): CRITICAL, SERIOUS, WARNING, INFORMATION or NONE.
4. | Customer comment – this is optional and may be changed – it is ignored by BurnInTest.
Comment lines may be inserted by using a “#” at the start of the line. These lines will be ignored by BurnInTest. An example is shown below: # PassMark BurnInTest,,, # Error message text and classification,,, 0,"No errors",NONE, 1,"Incorrect mathematical addition",SERIOUS, 2,"Incorrect mathematical subtraction",SERIOUS, 3,"Incorrect mathematical division",SERIOUS, 4,"Incorrect mathematical multiply",SERIOUS, 5,"Incorrect MMX addition",SERIOUS, 6,"Incorrect MMX subtraction",SERIOUS, 7,"Incorrect MMX multiplication",SERIOUS, 8,"Failed Windows call - Line Drawing",SERIOUS,