Plugin |
![]() ![]() ![]() |
The Plugin test is only included in the BurnInTest Pro version only. You can specify up to 5 external Plugin test applications . Run at the same time: Choose this option to run all Plugins at the same time Specify Plugin Appliction 1..5 Application Specifies the Plugin filename and command line arguments. See Available Plugin’s below for examples. Run as pre-test plugin Some Plugin tests may require manual user testing, for example, testing a keyboard. You can specify that a plugin be run before the main set of tests, such that the Plugin test will run, exit on completion of that test, and then the main set of tests will be run. This option is available for all Plugins.
Plugin’s available from Passmark PassMark has developed Plugins for touch screen, Modem, Keyboard and Firewire port testing. Touchscreen testing When PassMark’s MonitorTest is used as a BurnInTest Plugin, it tests in a pre-defined test sequence. MonitorTest shows a series of touch test displays that prompt the user to take certain actions to test the TouchScreen. PassMark MonitorTest allows single touch tests and multi touch pan, zoom, rotate and tap gesture tests. Version of Plugin required: PassMark MonitorTest V3.1 Build 1000 (or higher) Test name within BurnInTest displays and reports: Monitor. Test information displayed in BurnInTest: Status text, number of operations, errors and cycles, error text and severity. Application field should be set to: MonitorTest.exe /p Where: /p specifies MonitorTest to run as a plugin e.g. C:\Program Files\MonitorTest\MonitorTest.exe /p
Run as pre-test plugin: should be checked. Notes:
Keyboard testing When PassMark’s KeyboardTest is used as a BurnInTest Plugin, it tests in the Batch mode without collecting the manually entered information such as Keyboard Serial number. This mode allows automatic detection of all keys being successfully pressed, of User failure with User selected reasons. The keyboard can be failed at any time during the test or on requested user verification. A reason from a list of failure reasons will also be logged in BurnInTest. It should be noted that the KeyboardTest Keyboard Layout file (.kbl) needs to describe the keyboard you plan to test. This file describes all of the keys on the keyboard and is used (among other things) to determine when all the keys have been pressed and hence the trigger for automatically passing the keyboard. You may be able to use one of the default keyboards shipped with KeyboardTest, you may find a matching keyboard on our website Keyboard Layout Download Page or you may have to create your own .kbl file as described in the KeyboardTest help file. Version of Plugin required: PassMark KeyboardTest V2.2 1011 (or higher) Test name within BurnInTest displays and reports: Keyboard. Test information displayed in BurnInTest:.Status text, number of operations, errors and cycles, error text and severity. Application field should be set to: KeyboardTest.exe /p Where: /p specifies KeyboardTest to run as a plugin,in a modified batch mode e.g. C:\KeyboardTest\KeyboardTest.exe /p
Run as pre-test plugin: should be checked. Notes:
Battery Capacity testing The design capacity (max capacity at manufacture time) will be compared with the current charge capacity, so if the battery is fully charged but is less than the design capacity by the threshold amount an error will be flagged.
Application field should be set to: Battery_Capacity_Plugin.exe /t <value> OR Battery_Capacity_Plugin.exe /p <value> Where: /t <value> represents the value to be used when comparing the design capacity to the current capacity. Default value is 1000. /p <value> represents a percentage value when comparing the design capacity to the current capacity, eg /p 75 - an error will be logged if the current capacity is less than 75% of the design capacity.
Optional: /fc changes the comparison to use the fully charged capacity, instead of the default current charge, and compare it to the design capacity e.g. C:\Program Files\BurnInTest\Battery_Capacity_Plugin.exe /t 15000
Run as pre-test plugin: should be checked, this Plugin is designed to run before the other tests, without the need for user input. When using the "/fc" option some information field names and messages will be changed to reflect the different comparison values used (from "Current Charge" to "Full Capacity"). Sound testing This plugin will play a selected sound file and the tester can use the buttons to indicate if it played back correctly or not.
Application field should be set to: Sound_Plugin.exe /f <filename> Where: /f <filename> represents the audio file to be played, valid filetypes are MP3, WAV and MIDI.
e.g. C:\Program Files\BurnInTest\Sound_Plugin.exe /f TestMP3.mp3
Run as pre-test plugin & Run each separately: should be checked, this Plugin is designed to run before the other tests and requires user input to proceed. Microphone testing This plugin will display a window showing the available microphones with record and play buttons. Default recording settings of 2 channel - 24 bit - 192kHz are used, if this isn’t supported by the microphone the closest match is used (and recorded in the BurnInTest log). 10 seconds of audio will be recording and can then be played back.
Application field should be set to: Microphone_Plugin.exe No parameters are required
e.g. C:\Program Files\BurnInTest\Microphone_Plugin.exe
Run as pre-test plugin & Run each separately: should be checked, this plugin is designed to run before the other tests and requires user input to proceed. Webcam testing This plugin will display a window showing the available webcams and will display the video feed from the currently selected webcam.
Application field should be set to: Webcam_Plugin.exe No parameters are required
e.g. C:\Program Files\BurnInTest\Webcam_Plugin.exe
Run as pre-test plugin & Run each separately: should be checked, this plugin is designed to run before the other tests and requires user input to proceed.
|