befcb64a8e
Test fixtures can now automatically create required temporary or uncompressed raw disk images from provided url to be used as rootfs image. This allow tests with rw rootfs requirement to be executed repeatedly. TEST=run postgres test with new options BUG=b:257303497 Change-Id: If0537945beb427d15be0bec2f7a7d18daf595070 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4776167 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Zihan Chen <zihanchen@google.com> |
||
---|---|---|
.. | ||
benches | ||
fixture | ||
guest_under_test | ||
tests | ||
Cargo.toml | ||
README.md |
Crosvm End to End Tests
These tests run a crosvm VM on the host to verify end to end behavior. They use a prebuilt guest kernel and rootfs, which is downloaded from google cloud storage.
The e2e_tests can be executed by:
$ ./tools/run_tests2 --dut=vm -E 'rdeps(e2e_tests)'
Running with locally built kernel/rootfs
If the test needs to run offline, or you want to make changes to the kernel or rootfs, you have to
specify the environment variables CROSVM_CARGO_TEST_KERNEL_BINARY
and
CROSVM_CARGO_TEST_ROOTFS_IMAGE
to point to the right files.
The use_local_build.sh script does this for you:
$ source guest_under_test/use_local_build.sh
Uploading prebuilts
Note: Only Googlers with access to the crosvm-testing cloud storage bin can upload prebuilts.
To upload the modified rootfs, you will have to uprev the PREBUILT_VERSION
variable in:
./guest_under_test/PREBUILT_VERSION
and request a permission
to become a member of the crosvm-policy-uploader
group. Then run the upload script to build and
upload the new prebuilts. Never try to modify an existing prebuilt as the new images may break
tests in older versions.