mirror of https://github.com/aya-rs/aya
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
9ca0af1a79
This doesn't add any value; use `cargo build --tests` with `--message-format=json` instead; parse the output using `cargo_metadata` to discover the location of the test binary. Move test/integration-test/src/tests -> test/integration-test/tests to conform to https://doc.rust-lang.org/book/ch11-03-test-organization.html#integration-tests. |
1 year ago | |
|---|---|---|
| .. | ||
| integration-ebpf | 1 year ago | |
| integration-test | 1 year ago | |
| .gitignore | 2 years ago | |
| README.md | 1 year ago | |
| cloud-localds | 2 years ago | |
| run.sh | 1 year ago | |
README.md
Aya Integration Tests
The aya integration test suite is a set of tests to ensure that common usage behaviours work on real Linux distros
Prerequisites
Linux
To run locally all you need is:
- Rust nightly
libelf- A checkout of libbpf
cargo install bpf-linkerbpftool
Other OSs
- A POSIX shell
- A checkout of libbpf
rustup target add x86_64-unknown-linux-muslcargo install bpf-linker- Install
qemuandcloud-init-utilspackage - or any package that providescloud-localds
Usage
From the root of this repository:
Native
cargo xtask integration-test --libbpf-dir /path/to/libbpf
Virtualized
./test/run.sh /path/to/libbpf
Writing an integration test
Tests should follow these guidelines:
- Rust eBPF code should live in
integration-ebpf/${NAME}.rsand included inintegration-ebpf/Cargo.toml. - C eBPF code should live in
integration-ebpf/src/bpf/${NAME}.bpf.c. It's automatically compiled and made available as${OUT_DIR}/${NAME}.bpf.o. - Any bytecode should be included in the integration test binary using
include_bytes_aligned!. - Tests should be added to
integration-test/tests. - You may add a new module, or use an existing one.
- Test functions should not return
anyhow::Result<()>since this produces errors without stack traces. Prefer topanic!instead.