“Plugin” test [PLUGIN] |

(Applicable to BurnInTest Pro version only) If you have specialized hardware that BurnInTest does not test, you can write your own test and integrate it with BurnInTest. Up to 5 Plugin’s can be specified. PassMark has developed Plugins for the following tests:

- | Modem testing, using PassMark’s ModemTest software;

- | Keyboard testing, using PassMark’s KeyboardTest software,

- | Firewire port testing, using a PassMark developed Plugin and a “Kanguru FireFlash” drive.

- | Sample software in C and C++ is also available to assist developing a Plugin for your specific hardware.

The plug-in test will appear as another test, much like all of the tests. It may be switched on or off, and duty cycle set. The Plug-in application can define the following, which may be displayed, logged and included in the BurnInTest results:

- | The test window title text.

- | The number of test cycles completed.

- | The number of plug-in test errors in the current test run. The plug-in may flag BurnInTest when a new error occurs, and pass a plug-in defined error message (this will be displayed in the BurnInTest windows and may be logged in the log file).

- | The plug-in may flag BurnInTest when it wants to display new status text (defined by the plug-in), such as “Waiting for event”.

- | The Plug-in may define up to 3 “number of operations counts”. Typically this would be for something like, the number of writes, reads and verifies. All three operation counters may be given plug-in defined labels, which will be displayed in the BurnInTest test window. Any operation counter may be flagged as not in use, hence you could use a single operations counter, such as just “Write”. BurnInTest will display each label and number of operations counters separately in the test window. They will be summed for the main window operation count. These values are 64 bit integers.

- | 6 Plug-in defined string values and labels are provided for the display of other interesting data to the user, e.g. the plug-in could provide throughput in Mb/s to BurnInTest. BurnInTest displays this information in the test window. Both of these fields may be flagged as not in use.

Software may be written to interface an external plug-in test module with BurnInTest. An interface is defined to pass test parameters between an external test application and BurnInTest. BurnInTest will attempt to start this application when the Plug-in test is run and this application is specified as the Plug-in file. BurnInTest will pass a flag that indicates that the test run is still underway (e.g. has/ has not been stopped by the user) and BurnInTest will pass in the Duty cycle. Before starting the test, the plug-in application must initialize the test parameters (such as display labels) and flag that they have been set. Once the test is started, the test result parameters and most test window labels may be updated based on the test results. BurnInTest will pick up any changes. Specific cases where the Plugin must flag to BurnInTest that new parameters are available are for a new labels (as a group flag), error, a new status message and the user defined strings 1 & 2. You may need to check that BIT has read the old values before writing new values. See the Interface definition, PLUGININTERFACE, and the sample source code for details.