On Oct 27, 2009, at 5:15 PM, ext Bravo.Alex wrote: >> When you run your tests, you'd have the whole application debug log >> in > the application output pane, and a collection of the issues in the > "issues" pane. > > In order to easily parse QTestLib output, it's better to have it in > XML format. > But then outputting XML in Application Output is not going to be > very useful. > > In my opinion it's strange to present some info in one pane and > other info in another. > > What's wrong with taking the whole XML output and presenting it in > one consistent way in one place?
Well, I can't talk much about how QTestLib XML output works, because I've no idea. I suppose that tests could produce qDebug output, or qWarnings originating from Qt, and whatever dumped information, that are not only "Test XYZ failed at location foo" (or succeeded). What's the principal difference to compilation? There we have the full output of the compile process in one pane (Compile Output, allowing to inspect the inner workings to track down problems) and the collection of parsed issues in another (Build Issues, for easy interaction). ++ Eike > -----Original Message----- > From: qt-creator-boun...@trolltech.com > [mailto:qt-creator-boun...@trolltech.com > ] On Behalf Of Eike Ziller > Sent: Tuesday, October 27, 2009 3:48 AM > To: qt-creator@trolltech.com > Subject: Re: [Qt-creator] plugin_qtestlib > > > On Oct 26, 2009, at 8:39 PM, ext Coda Highland wrote: > >> Honestly I don't know if I want to set the precedent of allowing >> plugins to just arbitrarily add new tabs there. >> >> I think Build Issues would be a valid output target, though; it's >> already intended for jumping to the relevant places in the code and >> one could argue that failing a unit test is a build issue. > > One option is to put the test issues into what now is the "build > issues" pane: > > When you build a program, you have the whole build log in the compile > output pane, and a collection of the issues in the "issues" pane. > When you build your tests, you'd have the whole build log in the > compile output pane, and a collection of the issues in the "issues" > pane. > When you run your tests, you'd have the whole application debug log in > the application output pane, and a collection of the issues in the > "issues" pane. > This could be extended to also put issues when running other Qt > programs into the "issues" pane, like Qt warnings (connect failed, > etc, etc). > It would definitely make no sense to call it "build issues" then, but > anyhow, it's just a label. > And it would definitely make no sense to add yet another tab for > warnings when running Qt programs :) > > Another option is to extend the application output pane with clickable > links for Qt warnings, test result lines, and more. > > ++ Eike > >> >> /s/ Adam >> >> On Mon, Oct 26, 2009 at 2:18 PM, Robert Caldecott >> <robert.caldec...@gmail.com> wrote: >>> >>> I like the idea of a dedicated QTest output pane - will you be able >>> to double-click on failures to jump directly to the code? That >>> would be brilliant. >>> >>> 2009/10/26 Bravo.Alex <alex.br...@igt.com> >>>> >>>>> Plus that it's not so high in the list of things to do. >>>> >>>> >>>> >>>> If you are talking about qtcrea...@nokia team, it makes a lot of >>>> sense. >>>> >>>> But that's why you guys opened development to outside world, right? >>>> >>>> So that we can help you improve already great product. >>>> >>>> >>>> >>>> >>>> >>>> So, back to qtestlibplugin: >>>> >>>> After bringing it back from the dead, I realized that the >>>> architecture of this plugin might need adjustment: >>>> >>>> Right now it has its own type of output "Test Results" (just like >>>> "Build Issues", "Application Output" and 2 more). >>>> >>>> But, as this picture shows, there's not much space for different >>>> types of output: >>>> >>>> >>>> >>>> Besides it doesn't make much sense to "pollute" IDE's screen with >>>> "Test Results" button and list entry >>>> >>>> for applications that have nothing to do with QTestLib. >>>> >>>> >>>> >>>> It looks like there should be as little presence for this plugin >>>> as possible in the IDE's GUI. >>>> >>>> Ideally, this plugin should show itself only if output of a >>>> program is in QTestLib format. >>>> >>>> >>>> >>>> Thus this plugin really provides a different format of >>>> "Application Output", not a different output pane. >>>> >>>> >>>> >>>> So proposed adjustment to this plugin is to be able to have >>>> several formats of "Application Output". >>>> >>>> By default it's "raw" output, with the ability to switch to a >>>> different format. >>>> >>>> In case of qtestlibplugin it can be "test results" and "benchmark >>>> results" formats. >>>> >>>> Other plugins could have/add their own formats. >>>> >>>> >>>> >>>> What do you guys think? >>>> >>>> >>>> >>>> Alex >>>> >>>> >>>> >>>> >>>> >>>> -----Original Message----- >>>> From: qt-creator-boun...@trolltech.com >>>> [mailto:qt-creator-boun...@trolltech.com >>>> ] On Behalf Of Eike Ziller >>>> Sent: Monday, October 26, 2009 4:00 AM >>>> To: qt-creator@trolltech.com >>>> Subject: Re: [Qt-creator] plugin_qtestlib >>>> >>>> >>>> >>>> >>>> >>>> On Oct 20, 2009, at 7:24 PM, ext Bravo.Alex wrote: >>>> >>>> >>>> >>>>> Why is it dead: >>>> >>>>> a) it's obsolete, we now have a new XYZ plugin supporting >>>> >>>>> QTestLib in Qt Creator >>>> >>>>> b) the author is working on something else and doesn't have >>>> >>>>> time/interest to work on it >>>> >>>>> c) it didn't do much, so it's not worth maintaining >>>> >>>>> d) nobody needs it, we are satisfied with running tests >>>>> through >>>> >>>>> test.pl >>>> >>>> >>>> >>>> I suppose it's b) and c). Plus that it's not so high in the list of >>>> >>>> things to do. >>>> >>>> The only "maybe" still useful parts of the code in the plugin is >>>> >>>> probably the interaction/parsing of the QTestLib output. >>>> >>>> >>>> >>>> ++ Eike >>>> >>>> >>>> >>>>> Alex >>>> >>>>> >>>> >>>>> On Tuesday 20 October 2009 17:47:42 ext Bravo.Alex wrote: >>>> >>>>>> I'm not very successful in finding any info about >>>>>> plugin_qtestlib. >>>> >>>>>> There's not many comments in the source code either. >>>> >>>>>> >>>> >>>>>> plugins.pro says this: >>>> >>>>>> plugin_qtestlib \ # this seems to be dead >>>> >>>>>> >>>> >>>>>> The source tree on gitorious.org is missing >>>> >>>>> QTestLibPlugin.pluginspec for >>>> >>>>>> it. >>>> >>>>>> >>>> >>>>>> Does anybody know what it was supposed to do? >>>> >>>>> It's dead and the code probably is not very useful anymore either. >>>> >>>>> >>>> >>>>> daniel >>>> >>>>> >>>> >>>>> <ATT00001..txt> >>>> >>>> >>>> >>>> -- >>>> >>>> Eike Ziller >>>> >>>> Software Engineer >>>> >>>> Nokia, Qt Development Frameworks >>>> >>>> Phone +49 (0)30 6392 3255 >>>> >>>> Fax +49 (0)30 6392 3256 >>>> >>>> E-mail eike.zil...@nokia.com >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> >>>> Qt-creator mailing list >>>> >>>> Qt-creator@trolltech.com >>>> >>>> http://lists.trolltech.com/mailman/listinfo/qt-creator >>>> >>>> _______________________________________________ >>>> Qt-creator mailing list >>>> Qt-creator@trolltech.com >>>> http://lists.trolltech.com/mailman/listinfo/qt-creator >>>> >>> >>> >>> _______________________________________________ >>> Qt-creator mailing list >>> Qt-creator@trolltech.com >>> http://lists.trolltech.com/mailman/listinfo/qt-creator >>> >> >> _______________________________________________ >> Qt-creator mailing list >> Qt-creator@trolltech.com >> http://lists.trolltech.com/mailman/listinfo/qt-creator > > -- > Eike Ziller > Software Engineer > Nokia, Qt Development Frameworks > Phone +49 (0)30 6392 3255 > Fax +49 (0)30 6392 3256 > E-mail eike.zil...@nokia.com > > > > > > > _______________________________________________ > Qt-creator mailing list > Qt-creator@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-creator > > _______________________________________________ > Qt-creator mailing list > Qt-creator@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-creator -- Eike Ziller Software Engineer Nokia, Qt Development Frameworks Phone +49 (0)30 6392 3255 Fax +49 (0)30 6392 3256 E-mail eike.zil...@nokia.com _______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
