I have a question about use of a graphical front-end for a compiled language like C++.
I would think the point of a graphical front-end would be that you just leave it up, and peck the "Run Tests" button like a pigeon on steroids as you code.
But since you have to recompile your tests, you're going to have to close this window and launch it anew with every change, right?
It seems that what you'd really like is a *separate* application/script that runs and collects tests results, so that it can stay up as you work.
Comments?
Bob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The NEWS says look in examples/qt. There is no examples/qt.
There also appear to be no qt related symbols in libcppunit.so, nor are there any other libs installed.
Oops?
Bob
Ooops indeed. Forgot to add it to the tarball.
The qttestrunner library is located in src/qttestrunner.
The example is in examples/qt.
You can get it through the 'browse CVS repository' on the CVS page of sourceforge.
Thanks for reporting this,
Baptiste.
Ah, CVS. Thank you!
I have a question about use of a graphical front-end for a compiled language like C++.
I would think the point of a graphical front-end would be that you just leave it up, and peck the "Run Tests" button like a pigeon on steroids as you code.
But since you have to recompile your tests, you're going to have to close this window and launch it anew with every change, right?
It seems that what you'd really like is a *separate* application/script that runs and collects tests results, so that it can stay up as you work.
Comments?
Bob
I used to use the GUI (MFC & Qt). Nowadays, I use the CompilerOutputer and a text based TestRunner.
Error are printed in a compiler format, and you can jump to the first failed assertion with your IDE.
Change your makefile to run the test after building your application and you got very integrated unit testing plateform.
Check out examples/cppunitttest/CppUnitTestMain.cpp which does just that.
Baptiste.