-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Development: Add code coverage of unit tests as MAKE target #1279
Comments
First manual coverage result: 33 % (including the qt GUI source code):
Steps to create the code coverage:
To create an HTML report where you can even click on the py file names to see the code lines that are NOT covered so far use:
Note: The real coverage is higher since I have skipped unit tests for unknown reasons |
If I ignore the qt GUI source code files the coverage is 52 % (or higher due to some skipped unit tests in my setup):
|
Thanks a lot in your work for this. It seems to me that the Qt part is totally untested. But I still doing research about how to test Qt code. It is possible and I put it on my personal todo list as a far-away-job. |
Exactly. The way to go for "qt testing" could be
|
Closes #1279: Add code coverage of unit tests as MAKE target
Currently there are two
make
targets generated bycommon/configure
that executes all unit tests with different verbosity levels:It would be great to know how good the existing python code is covered by the unit test ("code coverage").
I propose to extend
common/configure
to generate a new make target for this:I am working on this... (hope it works in the end ;-)
The text was updated successfully, but these errors were encountered: