Name		Name	Last commit message	Last commit date
parent directory ..
codegen		codegen
runtime		runtime
testprogs		testprogs
CMakeLists.txt		CMakeLists.txt
README.md		README.md
ast.cpp		ast.cpp
bpftrace.cpp		bpftrace.cpp
clang_parser.cpp		clang_parser.cpp
main.cpp		main.cpp
main.py		main.py
mocks.cpp		mocks.cpp
mocks.h		mocks.h
parser.cpp		parser.cpp
parser.py		parser.py
probe.cpp		probe.cpp
runtime-tests.sh		runtime-tests.sh
semantic_analyser.cpp		semantic_analyser.cpp
tools-parsing-test.sh		tools-parsing-test.sh
tracepoint_format_parser.cpp		tracepoint_format_parser.cpp
utils.cpp		utils.cpp
utils.py		utils.py

README.md

bpftrace Tests

There are two test suites in the project.

These tests can be run with the bpftrace_test executable.

The code generation tests are based on the output of LLVM 5, so may give errors if run with different version. They can be excluded by running:

bpftrace_test --gtest_filter=-codegen*

Runtime tests will call the bpftrace executable.

Run: sudo make runtime-tests inside your build folder
By default, runtime-tests will look for the executable in the build folder. You can set a value to the environment variable BPFTRACE_RUNTIME_TEST_EXECUTABLE to customize it

You can add test programs for your runtime tests by placing a .c file corresponding to your test program in tests/testprogs.

The test file tests/testprogs/my_test.c will result in an executable that you can call and probe in your runtime test at ./testprogs/my_test

This intended to be useful for testing uprobes and USDT probes, or using uprobes to verify some other behavior in bpftrace.