Re: [Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread jason.mcdonald
David Heremans wrote: > So far I have used Qt in its most simple form. => one *.pro file to generate > one executable. > I've been reading about unit testing with qtestlib, but apparently for each > unit test one should build its own executable etc etc. Hi David, One unit test per executable is

Re: [Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread David Laing
Hi, Someone was asking about this on IRC the other day, and I pointed them here: http://developer.qt.nokia.com/videos/watch/introduction_to_automated_testing_for_qt_applications They found it quite useful. Cheers, Dave ___ Interest mailing list Inter

Re: [Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread Sergio Ahumada Navea
Hi, On 12/13/2011 09:10 PM, Scott Aron Bloom wrote: > My recommendation, that I use now... > > Swithc from QMake to CMake and use the google test system... > Just out of curiosity, what's the Google Test System ? Any link ? > Its 100% integrated into CMake, and it works great with Qt > > Scott >

Re: [Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread Scott Aron Bloom
My recommendation, that I use now... Swithc from QMake to CMake and use the google test system... Its 100% integrated into CMake, and it works great with Qt Scott -Original Message- From: interest-bounces+scott.bloom=onshorecs@qt-project.org [mailto:interest-bounces+scott.bloom=onsh

Re: [Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread Marc Mutz
On Tuesday December 13 2011, Konstantin Tokarev wrote: > > I think you mean the right thing, but FTR: QMake can't do more than one > > target per pro file. > > What is QMAKE_EXTRA_TARGETS than? I should have said "_build_ more than one target (library, application)." Obviously, qmake generates mu

Re: [Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread Konstantin Tokarev
13.12.2011, 21:47, "Marc Mutz" : > Hi Bo, > > On Tuesday December 13 2011, Bo Thorsen wrote: > >>  Den 13-12-2011 15:32, Frans Klaver skrev:       c) Is it possible to have multiple targets in one pro file ?       (And if so is this a Good Idea(TM)?) >>>  Can't remember, and usually not

Re: [Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread Marc Mutz
Hi Bo, On Tuesday December 13 2011, Bo Thorsen wrote: > Den 13-12-2011 15:32, Frans Klaver skrev: > >>      c) Is it possible to have multiple targets in one pro file ? > >>      (And if so is this a Good Idea(TM)?) > > > > Can't remember, and usually not. > > It is not only possible, but even my

Re: [Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread Bo Thorsen
Den 13-12-2011 15:32, Frans Klaver skrev: >> c) Is it possible to have multiple targets in one pro file ? (And if >> > so is this a Good Idea(TM)?) > Can't remember, and usually not. It is not only possible, but even my preferred method when using qmake. I have a top level pro file that loo

Re: [Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread Ben Lau
Hi David, I usually start a project with several modules. Each module will have its own directory and a .pri file. The .pri file will include the header , source , and add the current path to include / depended path. Then in the .pro file , call "include" to include those .pri file. Example pri

Re: [Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread Frans Klaver
On Tue, 13 Dec 2011 15:08:24 +0100, David Heremans wrote: > So far I have used Qt in its most simple form. => one *.pro file to > generate one executable. > I've been reading about unit testing with qtestlib, but apparently for > each unit test one should build its own executable etc etc. > > B

[Interest] Unit testing: any best-practices tips ?

2011-12-13 Thread David Heremans
Hello, So far I have used Qt in its most simple form. => one *.pro file to generate one executable. I've been reading about unit testing with qtestlib, but apparently for each unit test one should build its own executable etc etc. But how is this best implement in practice ? a) copy around al