fprintd/tests
Marco Trevisan (Treviño) cce9551c98 tests/fprintd: Be more flexible in accepting async results with exceptions
Some tests may have different behaviors depending on the CPU load when
using parallel tests, so async results could arrive in different order.

Then we need to accept multiple results:
  - A specific exception has to happen all the times
  - One of the accepted exception has to happen all the times
  - No exception or one of the allowed exception may happen

Depending on the test, use one of the possible strategies.
2021-01-25 18:18:40 +01:00
..
dbusmock tests: Check that PAM stops if the device could not be claimed 2020-12-07 15:27:14 +01:00
pam tests: Make tests executable 2021-01-13 14:47:00 +01:00
prints tests: Add test prints from libfprint 2019-12-03 17:08:03 +01:00
fprintd.py tests/fprintd: Be more flexible in accepting async results with exceptions 2021-01-25 18:18:40 +01:00
LSAN-leaks-suppress.txt build: Support running tests with address sanitizer 2020-04-01 13:58:08 +00:00
meson.build build: Don't add the utils tests under the daemon suite 2020-11-04 21:06:13 +01:00
output_checker.py tests: Add OutputChecker class to improve test code 2020-12-07 15:27:14 +01:00
test_fprintd_utils.py tests: Port test to use the OutputChecker 2020-12-07 15:27:14 +01:00
unittest_inspector.py tests: Add a tool to inspect the single python unit tests 2020-03-27 01:57:22 +01:00