commit d52caa50b916746d5fd37c5bd50c66f0cb076ee5
author Gaurav Shah <gauravsh@chromium.org> Tue Oct 25 10:46:03 2011 -0700
committer Gerrit <chrome-bot@google.com> Tue Oct 25 16:54:51 2011 -0700
tree 84b3688dc352e2f7d1fa3d6eb17ca34caf7216c5
parent 580c7af6aeddc277de482c7c60826bbce4e0a524

[shill] Update testing documentation for running a specific test

BUG=none
TEST=none

Change-Id: I9c6a20f55648f1b3ea73d96aa579a88de63e82fb
Reviewed-on: http://gerrit.chromium.org/gerrit/10667
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Commit-Ready: Gaurav Shah <gauravsh@chromium.org>
Tested-by: Gaurav Shah <gauravsh@chromium.org>

TESTING

diff --git a/TESTING b/TESTING
index 359c67d..88fd4d4 100644
--- a/TESTING
+++ b/TESTING
@@ -51,6 +51,13 @@
                             --remote=127.0.0.1 --ssh_port 9222 \
                             --args="config_file=wifi_vm_config" WiFiManager
 
+  To run a specific test out of the test suite, use test_pat option to --args.
+
+  # Example: To just run the 035CheckWEPKeySyntax test:
+  (chroot) src/scripts$ ./run_remote_tests.sh --board=x86-generic \
+                            --remote=127.0.0.1 --ssh_port 9222 \
+                            --args="config_file=wifi_vm_config test_pat=035CheckWEPKeySyntax" WiFiManager
+
 - configuration note: if you use a different port
   (e.g. hostfwd=tcp::9223-:22), you'll need to change:
     - the ssh_port argument to run_remote_tests
@@ -74,4 +81,4 @@
 [1] http://code.google.com/p/googletest/
 [2] http://code.google.com/p/googlemock/
 [3] http://autotest.kernel.org/,
-    http://www.chromium.org/chromium-os/testing/testing-faq
\ No newline at end of file
+    http://www.chromium.org/chromium-os/testing/testing-faq