add module testing

Test to load/unload modules multiple times to see if something bad
happens, which it shouldn't.

The majority of drivers registers themselves to an API that calls back
into the driver when the hardware side (or network protocol, file
system, etc) is getting detected or requested.

Loading and unloading modules that the DUT don't have hardware for is
likely to find more of the obvious bugs.

Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
2 files changed
tree: 6acd5b5e9a09ab639c80ba767225e3c638c36fae
  1. .github/
  2. .reuse/
  3. automated/
  4. docs/
  5. LICENSES/
  6. manual/
  7. mkdocs_plugin/
  8. plans/
  9. test/
  10. .gitignore
  11. .readthedocs.yml
  12. COPYING
  13. COPYRIGHTS
  14. mkdocs.yml
  15. README.md
  16. sanity-check.sh
  17. test.sh
  18. validate.py
README.md

Build Status REUSE Compliance Check

Test Definitions

A set of testing scripts designed to work with LAVA. Also contains test-runner script that allows execution outside LAVA.

More details in docs