tree: 1805279919910041ad48bfbac296f58dd516c119 [path history] [tgz]
  1. BUILD.gn
  2. README.md
  3. default.shard.cml
  4. meta/
  5. src/
  6. test_data/
  7. tests/
src/sys/test_runners/gtest/README.md

GTest Runner

Reviewed on: 2020-04-20

GTest Runner is a test runner that launches a gtest binary as a component, parses its output, and translates it to fuchsia.test.Suite protocol on behalf of the test.

Building

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

Examples

Examples to demonstrate how to write v2 test

To run this example:

fx run-test gtest-runner-example-tests

Concurrency

Test cases are executed sequentially by default. Instruction to override.

Arguments

Test authors can specify command line arguments to their tests in their component manifest file. These will be passed to the test when it is run.

Note the following known behavior change:

gtest_break_on_failure: As each test case is executed in a different process, this flag will not work.

The following flags are restricted and the test fails if any are passed as fuchsia.test.Suite provides equivalent functionality that replaces them

  • gtest_filter
  • gtest_output
  • gtest_also_run_disabled_tests
  • gtest_list_tests
  • gtest_repeat

Limitations

  • If a test calls GTEST_SKIP(), it will be recorded as Passed rather than as Skipped. This is due to a bug in gtest itself.

Partial Support

  • gtest runner supports printing stdout from the test but if a newline is not added at the end of every printf message, the developer will see some extra prints from gtest framework. This limitation will be solved with fxbug.dev/53955.

Testing

Run:

fx run-test gtest_runner_tests

Source layout

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