I saw something interesting:
If you have a look at the code coverage of gui/text, gui/kernel and
gui/opengl you can see that the code coverage in Qt5.4 is about 50% and
in Qt5/dev 0%!
This is really strange: the tests executed are mostly the same and some
of them are GUI tests.
Why this big
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
On 19/02/2015 17:31, Thiago Macieira wrote:
On Thursday 19 February 2015 15:57:30 Paeglis Gatis wrote:
Why can they be ignored?
I mean, we use only some of the API from that library, but bundle all of it.
If it is not fully covered by tests it is not an issue.
It's also possible that
.
*From:*
development-bounces+gatis.paeglis=theqtcompany@qt-project.org
development-bounces+gatis.paeglis=theqtcompany@qt-project.org on
behalf of Sébastien Fricker fric...@froglogic.com
*Sent:* Thursday, February 19, 2015 3:51
*From:*
development-bounces+laszlo.agocs=theqtcompany@qt-project.org
development-bounces+laszlo.agocs=theqtcompany@qt-project.org on
behalf of Paeglis Gatis gatis.paeg...@theqtcompany.com
*Sent:* Thursday, February 19, 2015 4:45 PM
*To:* Sébastien Fricker; development
*Subject:* Re
Hi,
The code coverage statistics of qtbase.git are now online again:
http://download.froglogic.com/public/qt5-squishcoco-report/
The build was broken due to the sanity check which was treating warnings
as errors.
Regards,
Sébastien
NOTE: if you see that something is broken, do not hesitate to
On 22.07.13 10:28, Saether Jan-Arve wrote:
I was looking at the bottom of the list and found for instance
qgraphicsanchorlayout.cpp to be down there.
It seems to be skipped because you haven't configured Qt as a
developer-build.
If possible, you should do add -developer-build to the
[mailto:development-bounces+jan-arve.saether=digia@qt-project.org]
*On Behalf Of *Sébastien Fricker
*Sent:* 12. juli 2013 10:38
*To:* development@qt-project.org
*Subject:* [Development] Qt Base code coverage statistics are now
computed on Ubuntu 11.04
Hi,
The test environment has changed and is now based
Hi,
The test environment has changed and is now based on Ubuntu 11.04.
The Puppet environment for a Qt CI test server is installed.
This permits to support tests which are using OpenGL, Dbus, network
infrastructures,
This permits to reach 5% more code coverage in comparison to the
Hi,
The new qtbase code coverage report is now available at
http://download.froglogic.com/public/qt5-squishcoco-report/
It is as usual computed on a daily base.
Changes:
1. The difference is computed between the origin/dev and origin/stable
branch of qtbase.git (before it was the the
For all you who have tried to install a network test server: a Puppet
configuration for Ubuntu 12.04 x64 is now available.
It's still in my personal Gitorious branch, as it still needs testing
before pushed through to production. Also I will flag these 12.04
changes so that we still have the
On 25.04.13 18:35, Richard Moore wrote:
On 25 April 2013 16:05, Thiago Macieira thiago.macie...@intel.com wrote:
On quinta-feira, 25 de abril de 2013 11.10.56, Diego Iastrubni wrote:
On Thu, Apr 25, 2013 at 9:29 AM, Sébastien Fricker
fric...@froglogic.comwrote:
Tony,
why not also
Am 22.02.2013 um 19:13 schrieb Thiago Macieira thiago.macie...@intel.com:
Note that we changed again the release procedures after complaints on how we
handled 5.0.1.
There will be no 5.0.2 tags until the final release.
I have updated the reference version, the next coverage report will
Rafal,
will you tag your Qt 5.0.2 RC?
If yes, I will provide a coverage report of QtBase between Qt 5.0.1 and this RC
Regards,
Sébastien
Am 22.02.2013 um 10:33 schrieb Motyka Rafal rafal.mot...@digia.com:
Hello,
We're planning to start Qt 5.0.2 framework testing on the 7th of March 2013,
Hi,
the Qt5 code coverage report is displaying now the code coverage report of the
modifications since Qt5.0.0.
So for QtBase 3 reports are now online:
The actual coverage report of the master branch (computed on a daily basis)
The code coverage of Qt5.0.0 (never updated)
The code coverage of
repository.
I agree that due to the fact that only one module is covered, it is a little
bit confusing.
Am 01.02.2013 um 10:52 schrieb Sergio Ahumada sergio.ahum...@digia.com:
On 02/01/2013 10:45 AM, Thiago Macieira wrote:
On sexta-feira, 1 de fevereiro de 2013 07.11.13, Sébastien Fricker wrote
qtsdk master doesn't make sense for daily reports because it only moves
during
release times. It would need to be the qt5.git repository and we go back to a
choice of the three branches.
So you would prefer to track the coverage of the dev branch of each module?
But this would not be
thiago.macie...@intel.com:
On sexta-feira, 1 de fevereiro de 2013 11.26.20, Sébastien Fricker wrote:
qtsdk master doesn't make sense for daily reports because it only moves
during release times. It would need to be the qt5.git repository and we
go back to a choice of the three branches.
So you
Hi,
the Qt5 code coverage report is displaying now the code coverage report of the
modifications since Qt5.0.0.
So for QtBase 3 reports are now online:
The actual coverage report of the master branch (computed on a daily basis)
The code coverage of Qt5.0.0 (never updated)
The code coverage of
Hi,
I had a try to follow
http://qt.gitorious.org/qtqa/sysadmin/blobs/master/README.network_test_server.txt
to setup the network test server for the code coverage statistic computation
(http://download.froglogic.com/public/qt5-squishcoco-report/)
I'm facing on an issue:
To reconfigure, run:
Bill,
this is corrected now:
http://download.froglogic.com/public/qt5-squishcoco-report/QtBase/source_543.html#line467
Regards
Am 08.10.2012 um 12:26 schrieb Sébastien Fricker fric...@froglogic.com:
Thanks Bill,
this is effectively not correct, the lines should be marks as executed.
Let me
One possible request: entry marking in the source reports, ie:
QString QMimeType::filterString() const
From:
http://download.froglogic.com/public/qt5-squishcoco-report/libQtWidgets/source_147.html
Was the test entered but the if lines not tested?
Another example: void
Hi,
providing a code coverage analysis of Qt is a living project and so we would be
happy of any feedback of the Qt developers.
Issues and suggestions can be addressed to the Squish Coco forum:
http://www.froglogic.com/forum/viewforum.php?f=10
We found that it is better to not put issues on
Overall the coverage was less than I expected, so I started reading the
source files list starting from lowest coverage and found some surprising
results, e.g. qmimedata.cpp 0% coverage, qsettings.cpp nearly 0%
coverage although I know there are tests for these.
In the execution list at
Would you include add-ons in the reports too?
Actually we start with QtBase. Of course in the future,
the goal is to provide an analysis on the whole Qt source.
Anyway to get run output logs from failed tests?
Good suggestion, will be present in the next daily coverage report.
Sébastien
25 matches
Mail list logo
