tast-tests: Let Chrome choose its own debugging port.

Make the local/chrome package pass --remote-debugging-port=0
when restarting Chrome and read the resulting port from
/home/chronos/DevToolsActivePort. This is apparently what
Telemetry does now.

BUG=none
TEST=added a unit test; ui.ChromeSanity also still passes

Change-Id: If7ad2bce48da64c762ba3b90c41bfebcb1009c12
Reviewed-on: https://chromium-review.googlesource.com/691102
Commit-Ready: Dan Erat <[email protected]>
Tested-by: Dan Erat <[email protected]>
Reviewed-by: Dan Erat <[email protected]>
3 files changed
tree: 002405b4c892e607a7b9bbf94d56bd81c3ab70d6
  1. src/
  2. README.md
README.md

Tast (tests)

This repository contains integration tests that are run by Tast.

Directory structure

  • src/chromiumos/tast/
    • local/ - main package for the local_tests executable containing “local” tests, i.e. ones that run on-device.
      • tests/ - Local tests, packaged by category.
      • ... - Packages used only by local tests.
    • remote/ - main package for the remote_tests executable containing “remote” tests, i.e. ones that run off-device.
      • tests/ - Remote tests, packaged by category.
      • ... - Packages used only by remote tests.

Shared code, the main tast executable, and documentation are located in the tast repository.

Package documentation is available at godoc.org.