KDevCppUnit draft

Friedrich W. H. Kossebau Friedrich.W.H at kossebau.de
Tue Jan 4 23:27:03 UTC 2005


Am Samstag, 9. Oktober 2004 19:44, schrieb Ewald Arnold:
> several weeks ago I posted my thoughts about a plugin for kdevelop to
> support unit testing. I got no response so I assume that no one else has
> started such a project,  maybe there is even no interest in using one.
> So I started myself and now have a prototype which is not really working
> yet but shows how it might look like as it contains some dummy data.
> I have a kde cvs account for several years from the times when I developed
> kvoctrain so I can commit myself. But I have been away from kde development
> quite a long time and don't want to commit in the wrong moment.
> So the question is: are there any objections to commit my draft which will
> be located at kdevelop/parts/cppunit?

Any progress on this? Noone except Arnold (and me) interested?

How would a testing framework be best implemented within KDevelop? Like with 
the make system, providing an abstract system integrated into KDevelop where 
all known testing frameworks (junit, qtunit, tut, homebrewn...) could be 
implemented for as plugins? But then most testing frameworks are also 

@Arnold: Is there any code to play with?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20050104/579f0d14/attachment.sig>

More information about the KDevelop-devel mailing list