Parametrize the keyboard test so that it can run in hwqual. Add to hwqual suite.

client/site_tests/suite_HWQual/README.txt

 Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 Use of this source code is governed by a BSD-style license that can be
 found in the LICENSE file.
 
 
 This document describes the steps to go through in order to run hardware
 qualification on a Chrome OS device under test (DUT).
 
 
 ================================================================================
@@ skipping 126 matching lines @@
   $ ./server/autoserv -r results.external_devices -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.external_devices
 
 
 * Run the system suspend/resume stability test:
 
   $ ./server/autoserv -r results.suspend_resume -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.suspend_resume
 
 
+* Run the keyboard semi-automated test by first reading the
+  instructions specified in the control file (control.keyboard) and
+  then executing:
+
+  $ ./server/autoserv -r results.keyboard -m <DUT_IP> -a hwqual \
+                  -c client/site_tests/suite_HWQual/control.keyboard
+
+
 * If the DUT has a Bluetooth adapter, run the Bluetooth semi-automated
   tests by following the instructions specified in the control file
   (control.bluetooth) and then executing:
 
   $ ./server/autoserv -r results.bluetooth -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.bluetooth
 
 
 * If the DUT has video out ports, run the Video Out semi-automated
   test by following the instructions specified in the control file
@@ skipping 69 matching lines @@
 * Make sure that there are no test failures in automatic,
   semi-automatic, or manual test categories.  Once all tests pass,
   package the result folders:
 
   $ tar cjf chromeos-hwqual-TAG-DATE.tar.bz2 results.*
 
   Send the tarball to your Google technical support contact for
   review.