| Age | Commit message (Collapse) | Author |
|---|
|
Adds new rules, launchers, and targets that enable the running of the
'HelloWorldTest' and `HelloWorldHostTest` from within the generated
Bazel environment.
Test: Manual testing, which can be performed with the following steps:
bazel run //build/pesto/experiments/prepare_bazel_test_env -- generate
bazel run //build/pesto/experiments/prepare_bazel_test_env -- sync
bazel test
//platform_testing/tests/example/jarhosttest:HelloWorldHostTest
--test_output=all --test_arg=--host
(The following command requires a connected device)
bazel run
//platform_testing/tests/example/instrumentation:HelloWorldTests
--test_output=all
Change-Id: I9414588dfe05f53cd4591185fdb3e7817face0d5
|
|
The cc_tf_test_launcher now checks the next positional argument for a
--host flag and adds the corresponding flags to the TradeFed execution.
This flag approach mimics how ATest currently handles host/device tests.
Test: Manual testing, through the following steps:
bazel run //build/pesto/experiments/prepare_bazel_test_env -- generate
bazel run //build/pesto/experiments/prepare_bazel_test_env -- sync
(For host side test)
bazel test //platform_testing/tests/example/native:hello_world_test
--test_output=all --test_arg=--host
(For device side test, requiring a device connected and lunch selecting
the correct build target)
bazel test //platform_testing/tests/example/native:hello_world_test
--test_output=all
Change-Id: I3b92a2551a1a9d272c45cd5047f5a764d8a849c7
|
|
The data/ directory includes the `static` and `templates`
directories which is used as the source for the generated Bazel
environment. Files placed in the template directory are formatted and
staged, and eventually synced to the source tree. Thus, they are stored
in the same directory hierarchy as the source tree. Files placed in the
static directory are copied into the source tree.
Test: N/A
Change-Id: I5adb3cd95e3142030287132b6ebc88d21da4f15c
|
