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.
aya/test
Tamir Duberstein b0a4ab5f20
xtask: Standardize command logging
Don't run `cargo build --verbose`; it's too noisy.
1 year ago
..
integration-ebpf bpf: improve bpf_probe_read_kernel_str_bytes and bpf_probe_read_user_str_bytes 1 year ago
integration-test xtask: Standardize command logging 1 year ago
.gitignore test: Replace RTF with Rust 2 years ago
README.md integration-test: Remove integration-test-macros 1 year ago
cloud-localds integration-tests: run on macos to get nested virtualization 2 years ago
run.sh Remove dependency on bpftool in integration tests 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:

  1. Rust nightly
  2. libelf
  3. A checkout of libbpf
  4. cargo install bpf-linker
  5. bpftool

Other OSs

  1. A POSIX shell
  2. A checkout of libbpf
  3. rustup target add x86_64-unknown-linux-musl
  4. cargo install bpf-linker
  5. Install qemu and cloud-init-utils package - or any package that provides cloud-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}.rs and included in integration-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 to panic! instead.