mirror of https://github.com/falcosecurity/falco.git synced 2026-03-19 03:06:22 +00:00

Files

Mark Stemm 910b8ff858 Fix(engine) Save parse positions when finding unresolved macros

Now that ASTs contain parse positions, use them when reporting errors
about unknown macros.

When doing the first pass to find all macro references, save macros as
a map<macro name,parse position> instead of a set<macro name>. While
making that change, change the visitor struct to use references
instead of pointers.

In the second pass, when reporting any unresolved macro references,
also report the parse position.

The unit tests also check that the positions of macros are properly
returned in the resolved/unresolved maps.

Signed-off-by: Mark Stemm <mark.stemm@gmail.com>

2022-12-01 17:03:52 +01:00

engine

Fix(engine) Save parse positions when finding unresolved macros

2022-12-01 17:03:52 +01:00

falco

refactor: drop civetweb dependency and implement healtz using cpp-httplib

2022-04-29 20:47:19 +02:00

CMakeLists.txt

tests: add unit tests for plugin requirements checks in the engine

2022-09-05 14:40:31 +02:00

OWNERS

docs: specify labels that apply to each area

2019-09-16 10:11:25 +02:00

README.md

docs(tests): fix typo

2020-05-14 15:02:15 +02:00

test_base.cpp

update: license headers

2019-10-08 16:02:26 +02:00

README.md

Falco unit tests

This folder contains the unit-tests suite for Falco. The framework we use for unit-tests is Catch2, while the one we use for mocking is FakeIt.

How to write tests

When you want to test a new file or test a non tested file, remember four steps:

The folder structure here is the same as the one in the userspace folder, so userspace/engine becomes tests/engine.
We call test files with this format test_<original-file-name>.cpp
Update the CMakeLists.txt file to include your file in FALCO_TESTS_SOURCES and change the FALCO_TESTED_LIBRARIES accordingly. You might also need to add dependencies, in that case, look at target_link_libraries and target_include_directories
If you are unsure on how to write tests, refer to our existing tests in this folder and to the Catch2 documentation.

How to execute tests

The suite can be configured with cmake and run with make.

In the root folder of Falco, after creating the build directory:

cd falco
mkdir build
cd build

You can prepare the tests with:

cmake ..

Optionally, you can customize the test suite by passing custom arguments like the examples below:

filter all tests containing the word ctor

cmake -DFALCO_TESTS_ARGUMENTS:STRING="-R ctor" ..

verbose execution

cmake -DFALCO_TESTS_ARGUMENTS:STRING="-V" ..

To see a list of all the custom arguments you may pass, execute ctest --help in your terminal.

Once you are ready, you can run your configuration with:

make tests