go/faft-running: Add note about tast tests
Previously, go/faft-running said that all FAFT tests are run via
test_that. This CL adds a breadcrumb to go/tast-running, which has
general information on running Tast tests with servo.
BUG=b:176554073
TEST=view in gitiles
Change-Id: Ie1473bcfba38d92eab81427911a92589ccdd6d15
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2957448
Auto-Submit: Greg Edelston <gredelston@google.com>
Tested-by: Greg Edelston <gredelston@google.com>
Reviewed-by: Andrew Luo <aluo@chromium.org>
Reviewed-by: Derek Beckett <dbeckett@chromium.org>
Commit-Queue: Greg Edelston <gredelston@google.com>
diff --git a/docs/faft-how-to-run-doc.md b/docs/faft-how-to-run-doc.md
index 7129a72..0015aa9 100644
--- a/docs/faft-how-to-run-doc.md
+++ b/docs/faft-how-to-run-doc.md
@@ -198,14 +198,18 @@
## Running Tests {#faft-running-tests}
+FAFT tests are written in two different frameworks: Autotest and Tast.
+
+Autotest tests are run using the `test_that` command, described below. Tast tests are run using the `tast run` command, which is documented at [go/tast-running](http://chromium.googlesource.com/chromiumos/platform/tast/+/HEAD/docs/running_tests.md).
+
### Setup Confirmation {#setup-confirmation}
-To run FAFT you use the `test_that` tool, which does not automatically start a
-`servod` process for communicating with the servo board. Running FAFT is easiest
-with `servod` and `test_that` running in separate terminals inside the SDK,
-using either multiple SDK instances (`cros_sdk --enter --no-ns-pid`) or a tool
-such as `screen` inside an SDK instance. Before running any tests, go into
-chroot:
+To run Autotest tests, use the `test_that` tool, which does not automatically
+start a `servod` process for communicating with the servo board. Running FAFT
+is easiest with `servod` and `test_that` running in separate terminals inside
+the SDK, using either multiple SDK instances (`cros_sdk --enter --no-ns-pid`)
+or a tool such as `screen` inside an SDK instance. Before running any tests, go
+into the chroot:
1. (chroot 1) Run `$ sudo servod --board=$BOARD` where `$BOARD` is the code name of the board you are testing. For example: `$ sudo servod --board=eve`
1. Go into a second chroot
@@ -225,7 +229,7 @@
### Sample Commands {#sample-commands}
-A few sample invocations of launching tests against a DUT:
+A few sample invocations of launching Autotest tests against a DUT:
Running FAFT test with test case name
