tree: 6790ac8d82b5a0800a1a156fce5285d6b6e6d1f9 [path history] [tgz]
  1. meta/
  2. src/
  3. test_data/
  4. tests/
  6. default.shard.cml

Inspect Test Runner

Reviewed on: 2021-04-22

Inspect test runner is a test runner that supports checking for the presence of specific Inspect properties on a system. The properties are checked from the global-system Archivist, and these tests should be run in isolation.


fx set core.x64 --with //src/sys/test_runners/inspect
fx build


Examples to demonstrate how to write an Inspect test:

To run this example:

fx test sample-inspect-tests


Test cases are executed concurrently, respecting the test suite parallel option. The outcome of all tests are pumped together until the referenced property is found or a configurable timeout is reached.

Program Arguments

Each Inspect test exists under the “programs/tests” key in the component manifest with the following structure:

program: {
    accessor: "ALL",     // Possible values: ALL, LEGACY, FEEDBACK.
    timeout_seconds: 60, // Timeout for these keys in seconds.
    cases: [
      "core/appmgr:root:version",  // A string selector ensures that the given property is present at all.
      "bootstrap/archivist:fuchsia.inspect.Health WHERE [a] a == \"OK\"", // Arbitrary comparisons are supported using Triage format.

For more information about the value of the expression key, see the Triage codelab.


No known current limitations.



fx test inspect-test-runner-unit-test

fx test inspect-runner-integration-test

Source layout

The entrypoint is located in src/, the FIDL service implementation and all the test logic exists in src/ Unit tests are co-located with the implementation. Integration tests are located in tests folder.