Modified the README.txt to include information about call_autoserv.py script.

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 Chrome OS
 hardware qualification on a device under test.
 
 ================================================================================
 Glossary
@@ skipping 63 matching lines @@
   a consistent starting point for the qualification tests and allows
   the system to collect cold boot performance metrics. Make sure you
   don't boot from USB.
 
 
 - Connect the DUT to the network and note its IP address <DUT_IP>. The
   IP address is displayed at the bottom of the network selection
   menu. Unless specified explicitly, the test setup works correctly
   through either wireless or wired network connections.
 
+- Unless otherwise noted, all tests can be performed on an AC-powered DUT.
+
+- Go to the Autotest server directory and clean up previous test results.
+
+  $ cd $HOME/chromeos-hwqual-TAG/autotest/
+  $ rm -rf results.*
+
+==============================================================================
+Automated and Semi-Automated Test Runs using utility script call_autoserv.py
+==============================================================================
+
+- Go back to parent directoy above autotest
+  
+  $ cd $HOME/chromeos-hwqual-TAG/
+
+- HWQual tests under .../autotest/client and .../autotest/server directories 
+  can be executed as following:
+
+  $ python call_autoserv.py --ip=<DUT_IP> --test=<HWQual test name>
+
+  <HWQual test name> - should be the exact name of the test without 'control.'
+  prefixed to the test name.
+
+  For example : To call control.auto test use the command as -
+    $ python call_autoserv.py --ip=<DUT_IP> --test=auto

[kmixter1, 2011/01/21 20:12:12]

Why explicitly call python?

+
+- The script will  do the following -
+  * Add testing_rsa.
+  * Set up ssh connection to the DUT.
+  * Search for the test name under autotest/client and autotest/server 
+    directories.
+  * Trigger the test exection.
+  * Save results in unique timestamped directoy and display its location.
+  * Run the ./generate_test_report script to display PASS / FAIL result output.
+  * In case of any FAIL / ERROR condition, will grab the result logs, tar them
+    up and display its location.
+
+==============================================================================
+Alternate way to run the HWQual tests

[kmixter1, 2011/01/21 20:12:12]

I suggest removing this and all the autoserv direct calls below.  Let's just
support this new, better way - but you'll need to be support it. :)

+==============================================================================
 
 - Add the DUT root private key to ssh-agent on the Autotest server:
 
   $ ssh-add $HOME/chromeos-hwqual-TAG/testing_rsa
 
 - If ssh-add fails saying that it cannot connect to your authentication agent,
   retry the command after running:
 
   $ eval `ssh-agent -s`
 
 - These commands allow the Autotest server to connect and login as root on the
   DUT.
 
 
 - Make sure you can ssh as root to the DUT from the Autotest
   server. The command below should print 0.
 
   $ ssh root@<DUT_IP> true; echo $?
 
 ================================================================================
-Automated and Semi-Automated Test Runs
+Automated and Semi-Automated Test Runs with precondition details
 ================================================================================
 
-- Unless otherwise noted, all tests can be performed on an AC-powered DUT.
-
-- Go to the Autotest server directory and clean up previous test results.
-
-  $ cd $HOME/chromeos-hwqual-TAG/autotest/
-  $ rm -rf results.*
-
-
 - Run the fully automated client-side tests:
 
   $ ./server/autoserv -r results.auto -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.auto
 
-
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=auto
+ 
 - Plug high-speed high-capacity storage devices in all USB and SD Card
   slots and run the external storage test:
 
   $ ./server/autoserv -r results.external_devices -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.external_drives
 
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=external_drives
+ 
 - Run the approved components test by first following the manual
   instructions specified in the control file (control.components) and
   then executing:
 
   $ ./server/autoserv -r results.components -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.components
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=components
+ 
 
 - 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
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=suspend_resume
+ 
 
 - If the DUT has video out ports, run the Video Out semi-automated
   test by following the instructions specified in the control file
   (control.video_out) and then executing:
 
   $ ./server/autoserv -r results.video_out.${PORT} -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.video_out
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=video_out
+ 
 - Where PORT is the name of each video port you are testing.  For
   example, if the DUT has one HDMI and one VGA out port, run:
 
   $ ./server/autoserv -r results.video_out.hdmi1 -m <DUT_IP> \
                 -c client/site_tests/suite_HWQual/control.video_out
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=video_out
+ 
   $ ./server/autoserv -r results.video_out.vga1 -m <DUT_IP> \
                 -c client/site_tests/suite_HWQual/control.video_out
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=video_out
+ 
 
 - Run the graphics tearing test:
 
   $ ./server/autoserv -r results.teartest -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.teartest
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=teartest
+ 
 - Run audio test, with built-in speakers and microphone
 
   $ ./server/autoserv -r results.audio -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.audio
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=audio
+ 
 - Plug-in headphone and microphone, run audio test again
 
   $ ./server/autoserv -r results.audio_ext -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.audio
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=audio
+ 
 - Run the Keyboard test : 
   (Wait several seconds after running the test. Then strike the "Search" key,
    e.g. the key above Left Shift and below Tab)
 
   $ ./server/autoserv -r result.keyboard -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.keyboard
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=keyboard
+ 
 - Run the DUT on AC. Probe the AC driver:
 
   $ ./server/autoserv -r result.probe_ac -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.probe_ac
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=probe_ac
+ 
 - Run the DUT on battery. Probe the battery driver:
   (If you just unplugged AC, please wait for a second before running
    the test for kernel updating power status.)
 
   $ ./server/autoserv -r result.probe_bat -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.probe_bat
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=probe_bat
+ 
 - Run the DUT on AC. Plug a power draw USB dongle in each USB port.
   Run the max power draw test:
 
   $ ./server/autoserv -r results.max_power_draw.ac -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.max_power_draw
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=max_power_draw
+ 
 - Run the DUT on battery. Plug a power draw USB dongle in each USB
   port. Run the max power draw test:
 
   $ ./server/autoserv -r results.max_power_draw.batt -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.max_power_draw
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=max_power_draw
+ 
 - Run the DUT on AC. Run the power settings test:
 
   $ ./server/autoserv -r results.power_x86_setting.ac -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.power_x86_settings
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=power_x86_settings
+ 
 - Run the DUT on battery. Run the power settings test:
 
   $ ./server/autoserv -r results.power_x86_setting.batt -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.power_x86_settings
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=power_x86_settings
+ 
 - Make sure the remaining battery charge is less than 5%. Note that the test
   will check and fail quickly if the initial battery charge is more than 5%.
   Run the DUT on AC. Run the battery charge test:
 
   $ ./server/autoserv -r results.battery_charge_time -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.battery_charge_time
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=battery_charge_time
+ 
 - Make sure that the battery is fully charged. Note that the test will not
   check if the battery is fully charged before running. Run the DUT on
   battery. Run the battery load test by first following the manual
   instructions specified in the control file (control.battery_load)
   and then executing:
 
   $ ./server/autoserv -r results.battery_load -m <DUT_IP> \
                   -c client/site_tests/suite_HWQual/control.battery_load
 
+  * Alternate method from outside autotest directory:
+    $ python call_autoserv.py --ip=<DUT_IP> --test=battery_load
+ 
 ================================================================================
 Reviewing Automated and Semi-Automated Test Results
 ================================================================================
 
 - Autotest logs progress and performance data in results.* directories
   specified through the '-r' autoserv option. The easy way to see a summary
   of your test results is to use the 'generate_test_report'
   script installed under $HOME/chromeos-hwqual-TAG/:
 
   $ ../generate_test_report results.*
@@ skipping 33 matching lines @@
 
   $ cd $HOME/chromeos-hwqual-TAG/autotest/
   $ cp ../manual/testcases.csv .
 
 - Package all results into a tar file:
 
   $ tar cjf chromeos-hwqual-results-TAG-DATE.tar.bz2 results.* testcases.csv
 
 - Send the resulting chromeos-hwqual-results file to your technical support
   contact.