mirror of https://github.com/aya-rs/aya.git synced 2026-05-26 11:24:23 +02:00

Files

T

History

swananan f10988d56a test: replace test-case with rstest

test-case relies on cooperating attribute macros when wrapping
generated parameterized tests. Stacking it with test_log can register
each generated case twice, so passing tests may run more than once and
mask order-sensitive or flaky behavior.

Move the parameterized tests to rstest, but do not rely on rstest's
implicit test-attribute detection. rstest treats attributes whose path
ends in test as test attributes; that has its own failure mode if a
non-test decorator matches, potentially producing cases that do not run
as intended.

Use explicit #[test_attr(...)] wrappers for every rstest case that
needs test_log or tokio, so generated tests get the intended harness
attribute instead of depending on implicit detection.

Refs: #1573.

2026-05-25 09:40:42 +00:00

integration-common

integration-test: cover fexit test-run

2026-05-23 07:40:55 +00:00

integration-ebpf

integration-test: cover fexit test-run

2026-05-23 07:40:55 +00:00

integration-test

test: replace test-case with rstest

2026-05-25 09:40:42 +00:00

.gitignore

test: Replace RTF with Rust

2022-07-03 14:33:24 +01:00

README.md

xtask: implement unit tests in VM

2025-12-31 05:01:43 -05:00

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 nightly
rustup target add {aarch64,x86_64}-unknown-linux-musl
cargo install bpf-linker
libelf-dev (libelf-devel on rpm-based distros)
llvm (for llvm-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_ARCHIVES>...

Writing an integration test

Tests should follow these guidelines:

Rust eBPF code should live in integration-ebpf/${NAME}.rs and included in integration-ebpf/Cargo.toml and integration-test/src/lib.rs using include_bytes_aligned!.
C eBPF code should live in integration-test/bpf/${NAME}.bpf.c. It should be added to the list of files in integration-test/build.rs and the list of constants in integration-test/src/lib.rs 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 to panic! instead.