delta/syslinux.git/com32/lib/syslinux/tests, branch master

tests: unit test bios_boot_linux()

2013-07-26T09:39:01+00:00

The constraints for allocating the kernel cmdline buffer under bios are
pretty involved and filled with historic rules. Unit test the bios linux
loader to ensure we never violate any of them, while at the same time
making sure we actually find a usable chunk of memory.

This commit is designed to test the changes in commit 77cadda8
("load_linux: dynamically calculate the cmdline region").

Signed-off-by: Matt Fleming

tests: syslinux_memmap_highest() unit tests

2013-07-26T08:54:47+00:00

Exercise the new syslinux_memmap_highest() function.

Signed-off-by: Matt Fleming

tests: delete test executables after each run

2013-07-24T12:58:24+00:00

The unit tests are designed to be small and should build very quickly,
so there should be no downside to rebuilding them for every run. The
upside is that we don't litter our build trees with target executables
and we don't need to explicitly list dependencies in Makefiles to ensure
our tests get rebuilt whenever a dependency changes.

Signed-off-by: Matt Fleming

tests: make mmap_entry globally available to unit tests

2013-07-24T11:00:11+00:00

There's a bunch of places that need to deal with mmap_entry entries when
doing tests, so make the structure readily available. Since we're going
to get a collection of header files that could be considered the
"unit test infrastructure" we might as well create a new directory for
them.

Signed-off-by: Matt Fleming

tests: Syslinux unit tests

2013-07-23T13:58:41+00:00

Improve our faith in the validity of the Syslinux code by writing unit
tests where possible. These should be used in addition to the regression
tests - unit tests are a means of doing very fine-grained testing of
code, whereas the regression tests are end-to-end tests that exercise
abstract functionality.

Unit tests run on your development machine and above all else, their
execution time should be kept to a minimum to encourage repeated runs of
the unit testsuite.

The Syslinux header hierarchy has been reconstructed under
tests/unittest/include. This allows us to reuse header files where
appropriate by simply creating a file with the same name and including
the original, e.g.

tests/unittest/include/com32.h:

  #include <../../../com32/include/com32.h>

Places where we need to override definitions (so that the tests build in
a dev environment) obviously won't include the original header file, but
such scenarios should be kept to a minimum, since you're not really
testing any Syslinux code that way.

To execute the collection of unit tests type,

  make unittest

Sample output might look like,

  Executing unit tests
      Running library unit tests...
        [+] zonelist passed
        [+] movebits passed
        [+] memscan passed

Signed-off-by: Matt Fleming