tast: Check data files are declared.

Make DataPath to check if a given file name is declared in Test.
Also, check the validity of file names in AddTest to catch errors
early.

This will avoid confusing "no such file or directory error" when
adding a new test because undeclared data files are not pushed to
DUT.

BUG=chromium:873952
TEST=fast_build.sh -T
TEST=tast run DUT example.DataFiles

Change-Id: Ica9e4ddfba7d4c9acfb184e2834952361ca8d7e8
Reviewed-on: https://chromium-review.googlesource.com/1175702
Commit-Ready: Shuhei Takahashi <nya@chromium.org>
Tested-by: Shuhei Takahashi <nya@chromium.org>
Reviewed-by: Shuhei Takahashi <nya@chromium.org>
5 files changed
tree: b4cf90c212dda44f65af30c608169c441d27a55b
  1. docs/
  2. src/
  3. tools/
  4. fast_build.sh
  5. README.md
README.md

Tast

Tast is an integration-testing system for Chrome OS. Its focus is on maintainability, speed, and ease of interpreting and reproducing test results. It supports building, deploying, and running tests. It doesn't implement other functionality like managing labs of devices used for testing, scheduling tests, or storing test results.

To try it out, see the quickstart document. The overview is a good starting point for learning more about how the system is structured.

Directory structure

This repository is organized in accordance with the Go in Chromium OS suggestions.

  • src/chromiumos/
    • cmd/local_test_runner/ - main package for the local_test_runner executable used to execute local test bundles on-device.
    • cmd/remote_test_runner/ - main package for the remote_test_runner executable used to execute remote test bundles on the host system.
    • cmd/tast/ - main package for the tast executable used to build and run tests.
      • ... - Packages used only by the tast executable.
    • tast/... - Common packages shared by multiple executables.

Tests are located in the tast-tests repository.

Documentation

For more details, see the docs subdirectory.

GoDoc