Test reporting

Top  Previous  Next

System information, test events, test results and temperature can by saved in test reports.

 

Reports can be a number of different formats:

Text (example).
HTML (example).
HTML Customer Test certificate (example).

Any or all of these report types can be selected to be created for a test run.

 

Test specific report information can be specified in the Report information (Machine identity) window. This allows a machine type, serial number and additional notes to be included in the reports. The Customer Test Certificate is meant as a single page summary for distribution to an end customer; as such additional information of the customer name and tester can also be specified to be included in this report.

 

The Customer Test Certificate report type uses a user configurable HTML template to allow the look and feel of the report to be customized. Customer specific information can also be included in the report by editing the HTML template provided in the BurnInTest installation package.

 

This report information can be generated automatically or manually:

Saved into a file automatically during a test. The level of detail can be specified (please see Test Preferences - Logging).
Saved into a file manually (please see File - Save Results Report).
Copied to the clipboard for pasting into another application (please see Edit - Copy clipboard and Pop-up menus).

 

Images may be captured from the BurnInTest tabs (e.g. Temperature) using the File - Save Window as Image option. The image formats EMF, GIF and BMP can be saved manually to a file or copied to the clipboard.

 

Detailed debug type reports can also be selected to help diagnose system problem. There are 2 levels of 'Activity Trace' logging. Level 1 activity trace logging mainly outputs additional information regarding error conditions, Level 2 trace logging outputs Level 1 content as well as a significant amount of activity reporting that helps understand specifically what the tests are doing in quite some detail (these files are generally very large). These reports can be selected to be in text or HTML format, however text files are generally easier to analyze post testing. Level 2 trace files can also include detailed information like Windows system and application events and detailed System memory information (example).