[PATCH 0/3] test: Try to deal with some co-dependent tests

Simon Glass sjg at chromium.org
Mon Feb 8 05:05:39 CET 2021


Tests are supposed to be independent. With driver model tests, the
environment is reset before each test, which ensures that.

With Python tests there is no reset of the board between tests, since we
want to run all the tests as quickly as possible and without needing the
external scripts running constantly.

In principle the Python tests can be independent if they each put the
world back the way they found it, but it turns out that some are not.
This means that some tests cannot be run unless another test is run
first. It also means that tests cannot be run in parallel, e.g. on
sandbox.

This series fixes some of them. Those that remain:

   test_gpt_swap_partitions - not sure?
   test_pinmux_status - not sure?
   test_sqfs_load - cannot be run more than once!
   test_bind_unbind_with_uclass - relies on previous test

The last one would be much better done as a C test, so it doesn't have
to deal with the changing driver tree. There isn't a lot of value in
running the test on a real board, since sandbox should find any bugs
in driver model or the 'bind' command.

If the above can be resolved we can enable parallel tests. On my test
machine (32 threads) it reduces the time from 38 seconds to 7.5s

To use this feature:
   pip3 install pytest-xdist

   test/py/test.py -B sandbox --build-dir /tmp/xx -q -k 'not slow' -n32


Simon Glass (3):
  test: Allow vboot tests to run in parallel
  test: Allow hush tests to run in parallel
  test: Allow tpm2 tests to run in parallel

 test/py/tests/test_hush_if_test.py | 20 ++++--------
 test/py/tests/test_tpm2.py         | 52 ++++++++++++++++++++++++++----
 test/py/tests/test_vboot.py        | 30 +++++++++--------
 3 files changed, 69 insertions(+), 33 deletions(-)

-- 
2.30.0.478.g8a0d178c01-goog



More information about the U-Boot mailing list