Batch mode testing

Keyboard Test may be run in batch mode. This allows testing of large numbers and types of keyboards in a methodical manner. It ensures useful test information is captured and saved in a test log file for future reference. Captured information includes, the test operator's identification, the keyboard product & batch identifications, the keyboard serial number and version.

When run in batch mode, Keyboard test now automatically detects test end passed. This together with user verification is logged to the test file for future reference. 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.

To run KeyboardTest in batch mode the "/b" command line argument should be used. That is, "KeyboardTest /b".

•	The user must enter the relevant text in each of the "Operator identification", "Product Identification" and "Batch identification" boxes.

•

The user may choose to enter a number of keystrokes required for a successful test. A key will be marked as properly tested only when the correct number of keystrokes has been met, no more, no less. This can help detect keys that only sometimes work or keys that bounce and register extra keystrokes. If this functionality is not wanted then leave this field blank and then any number of keystrokes will mark a key as okay.

•	The user must also enter a test log file name by either typing this directly into the "Filename" box (with full path included) eg. C:\KeyboardTest\keylog.log. Alternatively, the "..." button to the right of the Filename box can be pressed to browse for a particular file.

•

By selecting the "Overwrite log file" radio button, the user can specify that the log file be overwritten, with all previous data in this file lost. By selecting the "Append to log file" radio button, the user can specify that new test data be written at the end of the specified file, with all previous data in this file kept.

For each keyboard tested, the KeyboardTest Serial Number window will be displayed.

•	The user must enter the relevant text in each of the "Serial number " and "Version number" boxes.

Once testing a keyboard from the main KeyBoardTest window, the user may at any time fail the keyboard (and end the current keyboard test) by selecting the "Fail test" button.

•	The user should select the most appropriate reason for failure from the displayed list by selecting the radio button and pressing the Continue button. The failure reasons are shown below:

An automatic failure with the same result will occur if a Compound key defined with KTSTATUSFAIL is matched (may be used for testing hardware row or column shorts).

While testing a keyboard from the main KeyBoardTest window, if all defined keys have been successfully tested, the KeyboardTest Keyboard Passed ? window will be automatically displayed. Note that this will ignore compound keys, defined with KTSTATUSFAIL.

•	The user should either confirm that the keyboard did pass by selecting the "Yes - Pass Keyboard" button, or failing the keyboard by selecting the "no - Fail keyboard" button.

•	If the user confirms the keyboard has passed the keyboardTest Serial Number window will be displayed again for the next keyboard test.

•	If the user fails the keyboard, the KeyboardTest Fail Reason window will be displayed to allow a reason for the keyboard failure to be registered, before moving to the next keyboard test.

This logfile shows operator information followed by three tests (color coded to aid description). Note that the initally loaded keyboard is displayed, AT107.kbl, after the operator information. The first test shows a keyboard that was tested, passed automatically and verified to have passed by the user. The second shows a keyboard tested with test end automatically detected, but failed by the user as it had bad LEDs. The third shows a keyboard tested with no test end detected, but manually failed by the user, with the reason Bad key. Note that the user loaded the new keyboard layout, AT107new.kbl , after test 2.