This file is a compilation of the few various AppLabs text
files found in the tarball. These are made as one text file for quick and
easy online viewing. The text files which come with the testing programs
themselves are in separate folders in the tarball.

The various text files are separated with lines like:

>>> BEGIN KEYBOARD WORKSHEET <<<
>>> END KEYBOARD WORKSHEET <<<
>>> BEGIN TTCP TEST TOOL TEXT FILE <<<
>>> END TTCP TEST TOOL TEXT FILE <<<

The text files included in this file are:

keyboard_cert.txt

>>> BEGIN keyboard_cert.txt <<<

Keyboard Certification Worksheet
AppLabs' Keyboard Certification Test, Revision 1.0 - JCW

Tester Name: __________________________________________  Date: _______________


Section 1: Product Information

Manufacturer: ________________________________________________________________  
                                                                                

Product Name and Model Number: _______________________________________________  
                                                

Product Description: _____________________________________________ PS/2    USB  
                                                                

Overall Result:         PASS    FAIL

Details: _____________________________________________________________________
                                                                                
                                                                                
                                                                                
                                                        

Section 2: Setup Information

Hardware Testing Tools

System 1: ____________________________________________________________________

Make/Model ___________________ CPU _________ RAM _________ HD Space __________ 
                                                                               
System 2: ____________________________________________________________________
                                                                                
Make/Model ___________________ CPU _________ RAM _________ HD Space __________

 
Linux Distribution for this Test:

[ ] Caldera ___  [ ] TurboLinux ___   [ ] S.u.S.E. ___  [ ] Redhat ___




Section 3: Tests

Install With:                   PASS    FAIL
Get Setup Info:                                ___
Manufacturer Software:          PASS    FAIL   N/A
Manufacturer Documentation:     PASS    FAIL   N/A
Keyboard Functions:
   Console:                     PASS    FAIL
   X Server:                    PASS    FAIL




Section 4: Testing Procedures

Install With Test

Procedure: Tester installs the Linux distribution on a system while the system
is connected to the keyboard.

Determination:  The keyboard must allow continuous and infallible usage of the
connected system throughout the install process.  If at any time there is a loss
of keyboard control of the system, the test is a fail.


Get Setup Info

Procedure:  Tester is to get information on the testing system after the linux
distribution has been installed.  Tester should use the following commands and
save output to a file and print for attachment to this test document:

dumpkeys --short-info > key_info.txt

Determination: This is information collection and not a pass/fail test.  Once
the information has been collected, the tester should mark pass on the test
form to indicate the information has been collected.



Manufacturer Software Test

Procedure: Tester is to install the manufacturer's software and test according
to the capabilities of the software as described by the manufacturer.  All keys
and key combinations must be checked.

Determination: The software must work as described by the customer.  Any
non-functioning elements of the software package must be documented and
attached to the test form.  Failure of customer-specific software does not
effect the pass/failure state of the hardware (keyboard proper.)



Manufacturer Documentation

Procedure: Tester checks the documentation provided with the keyboard and
verifies the documentation adequately describes the installation and usage
of the product.

Determination: If documentation is needed, as determined by the complexity of
the product, and is included with the keyboard then the tester is to mark the
test as a pass; otherwise, fail.



Keyboard Functionality - console

Procedure: The tester is to cycle each key and key combination to determine
if the keyboard is returning the proper scancodes for key press and key release.
This is best done in a text editor or word processor.  For meta keys (Alt and
control, etc.) the tester can use the showkeys (showkey -a) program to determine
if the correct codes are being used.  If the manufacturer has submitted a test
plan for testing special keys on the keyboard, the tester is to follow the plan
and test the additional keys as directed by the plan.

Determination: Each key on the keyboard must print the proper character in the
text editor or word processor.  Meta keys must return the correct codes.  If any
key returns the incorrect character in either a text processor or via showkeys,
the test is a fail; otherwise, pass.



Keyboard Functionality - X Server

Procedure: The tester is to cycle each key and key combination to determine
if the keyboard is returning the proper scancodes for key press and key release.
This is best done in a text editor or word processor.  For meta keys (Alt and
control, etc.) the tester can use the showkeys (showkey -a) program to determine
if the correct codes are being used. If the manufacturer has submitted a test
plan for testing special keys on the keyboard, the tester is to follow the plan
and test the additional keys as directed by the plan.

Determination: Each key on the keyboard must print the proper character in the
text editor or word processor.  Meta keys must return the correct codes.  If any
key returns the incorrect character in either a text processor or via showkeys,
the test is a fail; otherwise, pass.


Resources:

The Linux keyboard and console HOWTO

>>> END keyboard_cert.txt <<<

If you have questions you can direct them to linux@applabs.com.