| .. | ||
| api | ||
| benchmark | ||
| devices | ||
| expect | ||
| full | ||
| jit-paging | ||
| kvm-unit-tests | ||
| manual | ||
| nasm | ||
| qemu | ||
| rust | ||
| Readme.md | ||
Use the corresponding make target in the root directory to run a test. The
following list is roughtly sorted from most interesting/useful to least.
- nasm: Small unit tests written in assembly, which are run using gdb on the host.
- qemu: Based on tests from qemu. Builds a Linux binary, which tests many CPU features, which are then compared to a run on qemu.
- kvm-unit-test: Based on tests from the KVM project, tests various CPU features.
- full: Starts several OSes and checks if they boot correctly.
- jit-paging: Tests jit and paging interaction.
- api: Tests for several API functions of v86.
- devices: Device tests.
- rust: Rust unit test helpers.
- expect: Expect tests for the jit output. Contains a set of asm+wasm files, where the jit is expected to produce the wasm file given the asm file.
The following environmental variables are respected by most tests if applicable:
TEST_RELEASE_BUILD=1: Test the release build (libv86.js, v86.wasm) instead of the debug build (libv86-debug.js, v86-debug.wasm)MAX_PARALLEL_TESTS=n: Maximum number of tests to run in parallel. Defaults to the number of cores in your system or less.TEST_NAME="…": Run only the specified test (only expect, full, nasm)