tree: 6c6d63b537624ccea5e321fd1054523d3c0cdd32 [path history] [tgz]
  1. cipd/
  2. cmd/
  3. testdata/
  4. BUILD.gn
  5. common_test.go
  6. driver.go
  7. driver_test.go
  8. manifest.go
  9. manifest_test.go
  10. OWNERS
  11. README.md
  12. sdk.go
  13. sdk_test.go
sdk/cts/tools/testdriver/README.md

Test Driver

This project aims to be a 1-click solution for executing CTS tests outside of the Fuchsia tree.

Running the CTS

  1. Add //sdk/cts to your fx args:

    fx set terminal.qemu-x64 --with //sdk/cts
    fx build
    
  2. Create a workspace for downloading artifacts:

    mkdir -p $CTS_WORKSPACE
    

The following commands will assume your workspace is located at $CTS_WORKSPACE

  1. Choose an SDK to target:

Currently, SDK version strings look like the following: X.YYYYMMDD.X.X

For example: This SDK version 3.20210308.3.1 matches this CIPD entry: https://chrome-infra-packages.appspot.com/p/fuchsia/sdk/gn/linux-amd64/+/GMIy21KF7lUXfC-C75Lwt0TG7fx2tVjk_5PRx_KT0kkC

You can view all SDK releases in CIPD: https://chrome-infra-packages.appspot.com/p/fuchsia/sdk/gn/linux-amd64/+/

The CTS is most beneficial when running against SDK versions that are newer than the test code, but the tool doesn't prevent you from choosing any SDK version.

  1. Run the tool using fx:

    fx cts --sdk_version $SDK_VERSION --workspace $CTS_WORKSPACE --manifest $MANIFEST_PATH
    

e.g. fx cts --sdk_version 3.20210308.2.1 --workspace ~/cts --manifest cts_manifest.json

Currently it just downloads the specified SDK and exits. Soon, this will start up an emulator, download all necessary artifacts to your workspace, and execute the CTS tests.