blob: 9b5eb5b4371199500b39eff713dda97143c652e7 [file] [log] [blame] [view]
# Create a new end-to-end test
This guide provides instructions on how to create a new end-to-end test using
the [Dart test library]({:.external} and
The guide creates an end-to-end test that prints Hello world!” in the log of a
Fuchsia device. Once you verify that you can build and run this test from your
machine, use the [resources](#edit-the-test) provided in this guide as reference
to further develop the test.
To create a new end-to-end test, the steps are:
1. [Create a new test](#create-a-new-test).
1. [Build the test](#build-the-test).
1. [Start the emulator](#start-the-emulator).
1. [Run the test](#run-the-test).
1. [Edit the test](#edit-the-test).
1. [Update and run the test](#update-and-run-the-test).
## Prerequisites
This guide requires that youre familiar with the following tasks:
* Configure and build a Fuchsia image to include an end-to-end test.
* Start the emulator ([FEMU](/docs/development/run/ with a Fuchsia
* Run an end-to-end test.
To learn about these tasks, see the
[Run an end-to-end test](/docs/development/testing/
## Create a new test {#create-a-new-test}
An end-to-end test needs to have the following directory structure and files:
├── test
│ └── <test_source_code_files>
├── pubspec.yaml
└── analysis_options.yaml
The instructions in this section create the minimum directory structure and
files necessary to build and run an end-to-end test.
Do the following:
1. Go to your Fuchsia directory, for example:
Note: If your Fuchsia source code is not located in the `~/fuchsia`
directory, replace `~/fuchsia` with your Fuchsia directory.
cd ~/fuchsia
1. Create a new branch, for example:
git checkout -b create_my_first_e2e_test
1. Go to the `//src/tests/end_to_end` directory:
cd src/tests/end_to_end
1. Create a new test directory called `my_e2e_test_example`, which has a `test`
mkdir -p my_e2e_test_example/test
1. Go to the new test directory:
cd my_e2e_test_example
1. Use a text editor to create a new `my_new_e2e_test.dart` file in the `test`
directory, for example:
vim test/my_new_e2e_test.dart
1. Paste the following code to `my_new_e2e_test.dart`:
import 'package:sl4f/sl4f.dart' as sl4f;
import 'package:test/test.dart';
void main() {
sl4f.Sl4f sl4fDriver;
setUp(() async {
sl4fDriver = sl4f.Sl4f.fromEnvironment();
await sl4fDriver.startServer();
tearDown(() async {
await sl4fDriver.stopServer();
test('tests hello world', () async {
await sl4f.DeviceLog(sl4fDriver).info('Hello world!');
print('Printed "Hello world!" in the device\'s log.');
}, timeout: Timeout(Duration(minutes: 1)));
The `test()` function in this code prints `Hello world!` in the devices
log, then the test outputs the `Printed "Hello world!" in the device's log.`
message on the host machines screen.
1. Save the file and exit the text editor.
1. Use a text editor to create a new `` file, for example:
vim ./
1. Paste the following code to ``:
dart_test("my_new_e2e_test") {
sources = [ "my_new_e2e_test.dart" ]
deps = [ "//sdk/testing/sl4f/client", "//third_party/dart-pkg/pub/test", ]
group("test") {
testonly = true
deps = [ ":my_new_e2e_test($host_toolchain)" ]
file defines the <code>test</code> target group to include
1. Save the file and exit the text editor.
1. Copy an existing `analysis_options.yaml` file to your test directory, for
cp ../sl4f/analysis_options.yaml .
The Dart compiler uses this file to identify compile warnings.
1. Create empty `pubspec.yaml`, `OWNERS`, and `` files:
touch pubspec.yaml OWNERS
Some text editors use the `pubspec.yaml` file to recognize that this test is
a Dart package. Provide the content of `OWNERS` and `` files later
when you contribue the test to the Fuchsia project.
## Build the test {#build-the-test}
Before you can run an end-to-end test, you first need to configure and build a
Fuchsia image to include the test in the build artifacts:
Note: The examples in this guide use the `terminal` product. End-to-end tests work with most
products except `core`.
1. Configure your Fuchsia image to include the `my_e2e_test_example` test
directory and the `test` target group:
fx set terminal.x64 --with //src/tests/end_to_end/my_e2e_test_example:test
`//src/tests/end_to_end/my_e2e_test_example` is the path to your new test
directory. The `test` target group, as defined in the `` file,
includes `my_new_e2e_test`.
1. Build your Fuchsia image:
fx build
When the `fx build` command completes, your build artifacts now include the
`my_new_e2e_test` end-to-end test, which you can run from your host machine.
## Start the emulator {#start-the-emulator}
Start the emulator to run your Fuchsia image:
Note: The steps in this section assume that you don't have any terminals
currently running FEMU or the `fx serve` command.
1. Configure an IPv6 network for the emulator (you only need to do this once):
sudo ip tuntap add dev qemu mode tap user $USER && sudo ifconfig qemu up
1. In a new terminal, start the emulator:
fx emu -N
1. Run the `fx set-device` command and select `step-atom-yard-juicy` (the
emulator’s default device name) to be your device, for example:
$ fx set-device
ERROR: Multiple devices found, please pick one from the list:
1) rabid-snort-wired-tutu
2) step-atom-yard-juicy
#? <b>2</b>
New default device: step-atom-yard-juicy
1. In another terminal, start a package server:
fx serve
## Run the test {#run-the-test}
In a new terminal, run the `my_new_e2e_test` end-to-end test:
fx test --e2e my_new_e2e_test
This test prints the following output:
00:00 +0: my_new_e2e_test tests hello world
Printed "Hello world!" in the device's log.
00:02 +1: All tests passed!
To scan the device’s log for the `Hello world!` string, run the `fx log` command
with the following options:
fx log --dump_logs yes --only Hello,world!
This command only prints the lines that contain `Hello` or`world!` from the
device’s log, for example:
[00770.760238][105502][105667][sl4f, parse_request] INFO: request id: String(""), name: "logging_facade.LogInfo", args: Object({"message": String("Hello world!")})
[00770.760356][105502][105504][sl4f, run_fidl_loop] INFO: Received synchronous request: Sender, MethodId { facade: "logging_facade", method: "LogInfo" }, Object({"message": String("Hello world!")})
[00770.760432][105502][105504][sl4f] INFO: "\"Hello world!\""
## Edit the test {#edit-the-test}
Edit the `my_new_e2e_test.dart` file to implement your test case.
Use the following resources for writing new tests:
* The [developer guide]({:.external} for writing
Dart tests.
* The source code of existing end-to-end tests, for example:
* <code>[screen_is_not_black_test.dart](/src/tests/end_to_end/screen_is_not_black/test/screen_is_not_black_test.dart)</code>
* The source code of the <code>[sl4f](/src/tests/end_to_end/sl4f/test/)</code>
end-to-end test, which tests various
[facades](/docs/concepts/testing/ in
[SL4F](/docs/concepts/testing/ See these tests to understand how
you may want to invoke some facades for testing certain features of a
Fuchsia product, for example:
* [Audio facade test](/src/tests/end_to_end/sl4f/test/audio_test.dart) -
Insert and capture audio on the device.
* [DeviceLog facade test](/src/tests/end_to_end/sl4f/test/device_log_test.dart) -
Read and write log messages on the device.
* [Performance facade test](/src/tests/end_to_end/sl4f/test/performance_test.dart) -
Enable collecting performance traces from the device, for instance, CPU
usage, Flutter frame rate, and kernel counters.
* [SetUI facade test](/src/tests/end_to_end/sl4f/test/setui_test.dart) -
Configure the device’s settings, for instance, a network interface
* [File facade test](/src/tests/end_to_end/sl4f/test/storage_test.dart) -
Read and write files on the device’s storage.
## Update and run the test {#update-and-run-the-test}
After editing the test’s source code, use the `fx test --e2e` command to run
the updated version of the test, for example:
fx test --e2e my_new_e2e_test
When this command detects any changes in the test’s source code, the command
automatically rebuilds the test prior to running the test.