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.
Updates the requirements on [network-types](https://github.com/vadorovsky/network-types) to permit the latest version. Updates `network-types` to 0.0.7 - [Release notes](https://github.com/vadorovsky/network-types/releases) - [Changelog](https://github.com/vadorovsky/network-types/blob/main/CHANGELOG.md) - [Commits](https://github.com/vadorovsky/network-types/compare/v0.0.7...v0.0.7) --- updated-dependencies: - dependency-name: network-types dependency-version: 0.0.7 dependency-type: direct:production dependency-group: cargo-crates ... Signed-off-by: dependabot[bot] <support@github.com> |
6 months ago | |
|---|---|---|
| .. | ||
| integration-common | 8 months ago | |
| integration-ebpf | 6 months ago | |
| integration-test | 7 months ago | |
| .gitignore | 3 years ago | |
| README.md | 10 months 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
You'll need:
rustup toolchain install nightlyrustup target add {aarch64,x86_64}-unknown-linux-muslcargo install bpf-linkerlibelf-dev(libelf-develon rpm-based distros)llvm(forllvm-objcopy)- (virtualized only)
qemu
Usage
From the root of this repository:
Native
cargo xtask integration-test local
Virtualized
cargo xtask integration-test vm --cache-dir <CACHE_DIR> <KERNEL_IMAGE>...
Writing an integration test
Tests should follow these guidelines:
- Rust eBPF code should live in
integration-ebpf/${NAME}.rsand included inintegration-ebpf/Cargo.tomlandintegration-test/src/lib.rsusinginclude_bytes_aligned!. - C eBPF code should live in
integration-test/bpf/${NAME}.bpf.c. It should be added to the list of files inintegration-test/build.rsand the list of constants inintegration-test/src/lib.rsusinginclude_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.