Google Git
Sign in
opensecura / 3p / sel4 / sel4test / refs/heads/master
commit6955396e371a18db446e57afb40bcb63c838ac61[log] [tgz]
authorSam Leffler <sleffler@google.com>Thu Feb 02 23:36:01 2023 +0000
committerSam Leffler <sleffler@google.com>Fri Feb 03 00:06:24 2023 +0000
treefcb156b98a3e5d4e043dbfe70b636a543610d847
parentf883392edfd1fcad9a659c1b1daad1a041dc4f2e [diff]
Revert "sel4test: enable elfloader/shoehorn fudge factor"

This reverts commit 7fc4940d1175a115c8520dca00bd393dd378d2b0.

Change-Id: I6b03f51d659b1150d6eaccb83dda986b6f72f9b0
1 file changed
tree: fcb156b98a3e5d4e043dbfe70b636a543610d847
  1. .github/
  2. apps/
  3. docs/
  4. integrations/
  5. libsel4testsupport/
  6. LICENSES/
  7. .gitignore
  8. .licenseignore
  9. CMakeLists.txt
  10. domain_schedule.c
  11. easy-settings.cmake
  12. LICENSE.md
  13. PREUPLOAD.cfg
  14. README.md
  15. settings.cmake
README.md

sel4test

Library for creating and running tests for seL4.

Setup

See the Getting Started page for instructions for installing required Host dependencies and how to checkout, build and run the tests in seL4test (this project).

Usage

Small unit tests can be defined anywhere, such as libraries outside of sel4test or in sel4test-driver. Larger tests that do things like creating processes need to be declared inside sel4test-tests.

Unit tests

To define a small unit test in a library outside of sel4test or in sel4test-driver:

  1. Declare libsel4test as a dependency for your library and include <sel4test/test.h>. You may also find the functions in <sel4test/testutil.h> handy.
  2. Write your tests. Then, for each test you want to run, call one of the macros that define a test, such as the DEFINE_TEST macro. They are declared here.
  3. Add your library as dependency to libsel4testsupport. Add a call to any function in your test file to testreporter.c in dummy_func(). If you have multiple test files, then you need to call one function for each test file.

For an example, take a look at libsel4serialserver/src/test.c in sel4_libs.

Assumptions

Currently unit tests are assumed to be running sequentially, standalone (i.e. not multi-threaded). Some tests rely on being the highest priority running thread in the system.

Other tests

To define a larger test in sel4test-tests:

  1. Place your test in apps/sel4test-tests/src/tests.
  2. Include <../helpers.h>.
  3. Write your tests. Then, for each test you want to run, call one of the macros that define a test, such as the DEFINE_TEST macro. They are declared here.

For an example, take a look at trivial.c in sel4test.