[Qt-interest] Unit tests the Qt way

Robert Caldecott robert.caldecott at gmail.com
Fri Dec 17 20:50:47 CET 2010


I am interested to know how the Qt team organize their unit tests.  I have
traditionally grouped together related tests into a single test project,
generating one executable.  For example, I have a library of useful shared
code containing a few dozen classes and helper functions and a single test
project that tests the lot.  However, after reading Yoann Lopes Qt Labs post
about auto-testing (
http://labs.qt.nokia.com/2010/10/29/making-auto-testing-easier/) I think I
may be going about this the wrong way and I should instead create a separate
project for each class that I want to test.  However, this would mean I
could, with some projects, end up with hundreds of separate projects, each
generating a different executable.

Can anyone offer me advice on the best way to manage unit tests?  If
separate projects are recommended then it means I could try the Qt
AutoTester which looks pretty neat but any real-world advice would be
welcome.

Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20101217/9797e055/attachment.html 


More information about the Qt-interest-old mailing list