[Development] Code Coverage Statistics for QtBase

Sébastien Fricker fricker at froglogic.com
Thu Feb 19 20:45:39 CET 2015

On 19/02/2015 17:39, Thiago Macieira wrote:
> On Thursday 19 February 2015 17:08:42 Sébastien Fricker wrote:
>> Is it possible that the default build parameter get changed between 
>> Qt5.4 and dev?
>> For example XCB support get detected automatically and the code get enabled?
> Yes for the EGL parts: it's possible the files are now built when they 
> previously weren't. I think it's the work that made EGL be supported with non-
> ES configurations. The same goes for the qevdev* and qfb* files.
> The OpenGL 4.4 and 4.5 files might be because your testing environment does not 
> support those profiles. Or they simply aren't tested, I don't know.
I'm just pointing that some new files are not covered.
I would not wonder me that the files are build and not used if the tests
are not directly use OpenGL, but the "old" X11 interface.
I prefer principally in such case not excluding it. But, if all CIs are
skipping EGL and OpenGL tests systematically, it might not be good at all.
> The qdbusmenu* and qdbustray* things are also probably environmental issues: 
> if your DE does not have a host for those specs, they wouldn't get activated.
Do you have a README which permits to set this?
> I can't explain why the qxcb* and font files.
> As forkfd.c reaching only 28% usage:
>  - part of the file is spawnfd, which wouldn't get used on Linux. I'll see 
> about dropping it from the build.
>  - a great deal of the code depends on timing of the OS scheduler, so it's 
> very hard to increase coverage. One way to do that is to launch a separate 
> process that keeps sending SIGCHLD periodically to the test process. 
> I think we already have a stress test that launches more than 16 concurrent 
> tests and would exercise the "big array", but I will check.
> PS: I'm working on clonefd with a colleague.
If you want I can generate a diff which compute what was covered in
Qt4.5 which is not covered in dev.
Just let me know.

PS: I'm next week on vacation, so I'm not sure that I can do a fast reply.


More information about the Development mailing list