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.

History

Dave Tucker 8780a50be1 .github: Add markdownlint This adds a linter to catch common markdown formatting errors. The linter used is markdownlint-cli2 which is available on all platforms and has an associated Github Action to automate these checks in CI. Configuration is checked in at .markdownlint-cli2.yaml. You may run the check locally using `markdownlint-cli2`. Or you may install the extension for VSCode: DavidAnson.vscode-markdownlint Signed-off-by: Dave Tucker <dave@dtucker.co.uk>		10 months ago
..
integration-ebpf	aya-log: fix hygiene	11 months ago
integration-test	github: run integration tests on local kernel	11 months ago
.gitignore	test: Replace RTF with Rust	2 years ago
README.md	.github: Add markdownlint	10 months ago

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:

From the root of this repository:

cargo xtask integration-test local

cargo xtask integration-test vm

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.