Rob Blanckaert 58d4336149 virtio_net device hai 4 meses
..
api 860de55db8 refactor vga code hai 1 mes
benchmark 6e4f6754b6 enable screen dummy by default hai 1 mes
devices 58d4336149 virtio_net device hai 1 mes
expect 03a9b89ffb rename start_eip to eip_offset_in_page and consistently mask off upper bits hai 1 mes
full 860de55db8 refactor vga code hai 1 mes
jit-paging fcdd110cb7 Clean up some tests hai 1 mes
kvm-unit-tests a66e3a2bfb fewer blank lines hai 3 meses
manual 080482da89 s/V86Starter/V86 hai 1 ano
nasm 5435c2f8c4 s/==/=== hai 4 meses
qemu fcdd110cb7 Clean up some tests hai 1 mes
rust acb8ad5423 Avoid console.assert (doesn't throw) %!s(int64=3) %!d(string=hai) anos
Readme.md 2697aa6192 Document env variables for tests %!s(int64=3) %!d(string=hai) anos

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)