4 Commits

Author	SHA1	Message	Date
Zbigniew Jędrzejewski-Szmek	6b908313ef	test/run-unit-tests: make script compatible with python3.6 ... dataclasses were added in python3.7, but bionic has python3.6. Yes, the new code is a travesty, but it does the job. Fixes #19640.	2021-05-18 23:59:05 +02:00
Dan Streetman	d57e871c60	test: combine stdout/stderr from failed test ... Printing stdout and stderr from a failed test makes it harder to interpret what the specific problem was; instead let's print out the lines in order as we got them when the test was run Also save failed test output to file if ARTIFACT_DIRECTORY is defined	2021-05-15 11:49:24 +01:00
Zbigniew Jędrzejewski-Szmek	f5acf84dbe	run-unit-tests: add option to run unsafe tests too	2018-09-24 15:42:50 +02:00
Zbigniew Jędrzejewski-Szmek	3762f8e316	tests: add a runner for installed tests ... We have "installed tests", but don't provide an easy way to run them. The protocol is very simple: each test must return 0 for success, 77 means "skipped", anything else is an error. In addition, we want to print test output only if the test failed. I wrote this simple script. It is pretty basic, but implements the functions listed above. Since it is written in python it should be easy to add option parsing (like running only specific tests, or running unsafe tests, etc.) I looked at the following alternatives: - Ubuntu root-unittests: this works, but just dumps all output to the terminal, has no coloring. - @ssahani's test runner [2] It uses the unittest library and the test suite was implented as a class, and doesn't implement any of the functions listed above. - cram [3,4] cram runs our tests, but does not understand the "ignore the output" part, has not support for our magic skip code (it uses hardcoded 80 instead), and seems dead upstream. - meson test Here the idea would be to provide an almost-empty meson.build file under /usr/lib/systemd/tests/ that would just define all the tests. This would allow us to reuse the test runner we use normally. Unfortunately meson requires a build directory and configuration to be done before running tests. This would be possible, but seems a lot of effort to just run a few binaries. [1] 242c96addb/debian/tests/root-unittests [2] https://github.com/systemd/systemd-fedora-ci/blob/master/upstream/systemd-upstream-tests.py [3] https://bitheap.org/cram/ [4] https://pypi.org/project/pytest-cram/ Fixes #10069.	2018-09-24 15:42:50 +02:00