You'll need a Chrome OS chroot.
You‘ll also need a Chrome OS device running a system image built with the test
flag that’s reachable from your workstation via SSH. An image running in a virtual machine will also work.
In your chroot, run the following:
tast -verbose run -build=false <test-device-ip> ui.ChromeSanity
You should see output scroll by on your workstation, and on the Chrome OS device, the test should log in and load a webpage. After the test is done, take a look at the results in /tmp/tast/results/latest
in your chroot.
The previous step ran a test that was already built into your device's system image, but you can also use the tast
command to quickly rebuild all tests and push them to the device.
In your chroot, run the same command as before but without the -build=false
argument:
tast -verbose run <test-device-ip> ui.ChromeSanity
This time, the command will take a bit longer (but build objects will be cached). The test should succeed again.
The first time you run this, or after you sync your checkout, you may see an error similar to the following:
To install missing dependencies, run: sudo emerge -j 16 \ =dev-go/cdp-0.9.1-r1 \ =dev-go/dbus-0.0.2-r5
This is expected: to speed things up,
tast
is building the tests directly instead of emerging thetast-local-tests
package, so it needs some help from you to make sure that all required dependencies are installed. If you run the providedemerge
command, thetast
command should work when re-run.
See Running Tests for more information.
Now, let's modify the test. In your Chrome OS checkout, go to src/platform/tast-tests/src/chromiumos/tast/local/tests/ui
and open chrome_sanity.go
. The ChromeSanity
function here will run directly on the test device.
At the end of the function, add the following code:
if _, err = cr.NewConn(s.Context(), "https://www.google.com/"); err != nil {
s.Error("Failed to open page: ", err)
}
Back in your chroot, run tast
again:
tast -verbose run <test-device-ip> ui.ChromeSanity
This time, the test should additionally open a Google search page.
Return to the test file and add the following statement at the end of the function:
s.Error("This is an intentional error")
If you build and run the test again, you should see it fail.
See Writing Tests for more information.
Many resources are available for learning more about Go. Here are a few: