Keyboard Test Cases (Windows CE 5.0)
The Keyboard Test executes the tux –o –d kbdtest command line on default execution. This test has no additional functionality that you can add by modifying command-line parameters.
Prior to running each test case, a dialog box prompts you to confirm that you want to continue with the test. All test cases require you to interact with the test. Follow the instructions on the screen in order to complete the tests.
After running test cases 50, 53, and 54, the test prompts you with a question regarding the status of the test. If you choose Yes, the test is logged as passing. If you choose No, the test prompts you to run the test case a second time. If you choose No a second time, the test is logged as failing.
Test cases 51, 52, and 55 detect failure without your interaction and time out if no input is registered. If a failure is detected in these test cases, the test prompts you to run the test again. If you choose No, the test is logged as failing.
The following table shows the test cases for the Keyboard Test.
| Test case | Description |
|---|---|
| 50: Manual key press | Displays keyboard events on the screen as they occur. This allows you to verify that the keyboard events are correctly recognized. Press the spacebar as indicated in the test to end the test. This test case fails only if you choose No at the end of the test. |
| 51: Key sequence check | Tests the ability to detect key input properly. This test requires you to press keys on the keyboard. Press each key in the order specified when prompted. This test case fails if you input an incorrect keystroke and then choose No when prompted to run the test a second time. |
| 52: Key chording | Tests the ability to detect certain key combinations properly. This test prompts you to press keys on the keyboard in a specified order. This test fails if you input incorrect keystrokes and then choose No when prompted to the test a second time. You must press and hold down keys that are part of a key combination. For example, when prompted to press <CTRL-ALT-A>, press and hold the CTRL key, press and hold the ALT key, and then press the A key. You can then release all keys. |
| 53: Text Editing | Provides a text box that allows you to test all keys manually. When this test is finished, choose the box near the top of the screen to continue. This test fails only if you choose No at the end of the test. |
| 54: Repeat rate and key delay | Tests the ability to speed up and slow down the key repeat rate and the ability to increase and decrease the delay before repeat. The test requires you to observe and remember the repeat rate and key delay and to respond to questions accordingly. This test fails only if you choose No when prompted. |
| 55: Async key test | Tests that specific keys on the keyboard are detected properly. This test prompts you to press keys on the keyboard in a specified order. This test fails if you input an incorrect keystroke and then choose No when prompted to the test a second time. |
Remarks
This test library can have one or more optional command-line entries to change the behavior of the test. To specify one or more optional command-line entries to the test library, you must use the –c command-line option. This option forces Tux to pass the specified string into the test library.
See Also
Send Feedback on this topic to the authors