On Thu, 2022-09-29 at 12:44 +0000, c.buhtz@posteo.jp wrote:
can we have a test folder like "qt/test" as an equivalent to "common/test"?
sure, I would add my tests there too (later)
I tried to understand the configure files in "qt" and "common"
If you need help here I can support you (I guess you want to extend the test* make targets in "configure").
I would like to have a "qt/test/test_qt.py" that only does an "import PyQt5" and doesn't raise an ImportError.
What is the purpose of this since it tests the Python environment/setup but not BiT itself
[...] I would like to add a qt-import-test that would fail if someone else in the future mess up the travis config.
I am not sure I understand this right. Is the intention here to "test" that TravisCI has all required packages (qt...) installed?