tast-tests: Ensure mash is running in ui.MashLogin

Pass --enable-features=Mash to chrome instead of the deprecated --mash.

Verify that at least one chrome process is running with
--mash-service-name, which implies that a mash process has started
(usually the ash_and_ui process, but that may change).

BUG=chromium:670064
TEST=tast ui.MashLogin

Change-Id: Icd1b73dc78c8d0feaa6f0a78e9d2c6c6bc26390d
Reviewed-on: https://chromium-review.googlesource.com/972154
Commit-Ready: James Cook <jamescook@chromium.org>
Tested-by: James Cook <jamescook@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
2 files changed
tree: a4a66031aa3c304eb2ad77885ac7820f0db0a054
  1. src/
  2. .gitignore
  3. README.md
README.md

Tast (tests)

This repository contains integration tests that are run by Tast.

Directory structure

  • src/chromiumos/tast/
    • local/ - Code related to local (i.e. on-device or “client”) tests.
      • bundles/ - Local test bundles.
        • cros/ - The “cros” local test bundle, containing standard Chrome OS tests. Tests are packaged by category.
      • ... - Packages used only by local tests.
    • remote/ - Code related to remote (i.e. off-device or “server”) tests.
      • bundles/ - Remote test bundles.
        • cros/ - The “cros” remote test bundle, containing standard Chrome OS tests. Tests are packaged by category.
      • ... - Packages used only by remote tests.

Shared code, the main tast executable, the local_test_runner and remote_test_runner executables responsible for running bundles, and documentation are located in the tast repository.

GoDoc