I tried to run pytest (via "./configure && make test") on my local repo
BiT uses "unittest", not "pytest"
I thought "configure" and/or "make" will take care of that and minimally warn me about missing dependencies?
This is up to the developer of ./configure to check this and warn about it during "make". Since BiT is python-based (= an interpreted language) missing dependencies do pop up only if you run the code line that imports the (missing) module to provoke an error about this missing dependency. That is why code coverage of unit tests is also helpful to discover missing dependencies... On my local machine the unit tests pass with "make test" as well as "python -m unittest -b" (from within the common folder !!!):
python -m unittest -b .................................................................................................................................ss......................................................................s.......................s..........sssssssssssssssssssssssss...ssssss.........sssssssss.....s.......s..s......s...................s.s...ss...s.............
Ran 356 tests in 7.542s OK (skipped=53) /usr/lib/python3.8/subprocess.py:946: ResourceWarning: subprocess 379551 is still running ~/dev/backintime/common
Can I setup the make-pytest-thing in a way that the hugh output is logged into a file?
"python -m unittest -b" creates a summarized output ("make test" calls every unit test separately which produces lengthy output)... You could redirect the result into a file