blob: be654995aede318af8710b051f404508b7bc5113 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
# Integration Tests
End-to-end integration tests for ior. A standalone I/O workload binary performs
deterministic syscalls, ior traces the workload by PID via BPF, and the test
harness asserts the captured `.ior.zst` output matches expectations.
## Prerequisites
- Built `ior` binary (`mage all`)
- Root privileges or `CAP_BPF` (required for BPF tracepoint attachment)
The binary embeds its default BPF object. Set `IOR_BPF_OBJECT=/path/to/ior.bpf.o`
only when you explicitly want to override the embedded object during testing.
## Running
```bash
mage integrationTest
```
This builds everything (ior, ioworkload) and runs integration tests in parallel.
Default parallelism is `NumCPU * 2` (minimum `1`).
Tests automatically skip with `t.Skip` when not running as root.
To run serially (useful for debugging/flaky triage):
```bash
mage integrationTestSerial
```
Tune parallelism by setting `INTEGRATION_PARALLEL`, for example:
```bash
INTEGRATION_PARALLEL=4 mage integrationTest
```
## Structure
- `cmd/ioworkload/` — Standalone binary performing known I/O patterns
- `harness.go` — Test orchestration (start ior + workload, collect output)
- `parse.go` — Parse `.ior.zst` into assertable `TestResult`
- `expectations.go` — `ExpectedEvent` type and assertion helpers
- `*_test.go` — One file per syscall family
See `../INTEGRATIONTESTS-PLAN.md` for the full design.
|
