[Development] Introducing QtMetrics

[Sarajärvi Tony]

Hi

I have the task of automating that database so that it is updated after every build. Semi-easy thing to do, just haven't had time to do that yet. Great to hear it's expected though, now I can prioritize it higher ;)

I have also begun the work on changing the data, so that it doesn't only print the information per test set (tst_*) as it does now, but it would also show the individual test cases (the ones that show up PASS, XFAIL or SKIP in log). This would give real time information that's manually currently gathered on a wiki page: http://qt-project.org/wiki/CI_Failing_Tests

Also a list of all test cases that have been skipped or have failed _as expected_ is under way. I'll also try to parse automatically the QTBUG-xxxxx string so that it would show up when available.

Different URLs to different sub-pages was something on the TODO list for the QtMetrics page. Unfortunately we had to draw the line somewhere, so that our developer could continue documenting his thesis work. Hopefully he or someone else continues his work on the web page.

Regards,
-Tony

> -----Original Message-----
> From: Hausmann Simon
> Sent: 17. heinäkuuta 2013 17:22
> To: development at qt-project.org
> Cc: Sarajärvi Tony
> Subject: Re: [Development] Introducing QtMetrics
> 
> On Tuesday 4. June 2013 10.13.16 Sarajärvi Tony wrote:
> > Hi
> >
> > We are ready to launch our QtMetrics page for the public now.
> 
> Great stuff!
> 
> [...]
> > Note 2: The data you see is currently manually kept up to date about once a
> > day. This will be changed as soon as we have time to implement an automated
> > function for this that triggers after a build.
> 
> For me this one is going to be the game changer :). I've used the dashboard in
> the past weeks to tyr to get a better overview of the test failures of a topic
> branch, and the infrequent updates are what makes it a bit harder to work
> with. I hope you'll find time soon to implement automatic frequent updates of
> the database :)
> 
> 
> The only other thing that comes to my mind that would be nice to improve is
> the lack of a state changes in the UI being reflected in the URL, making it
> impossible for example to copy & paste the url to somebody to show them the
> current "state".
> 
> Simon