Re: Re: Re: Re: Re: Unit Testing is vital

With revision 75 the dependencies between tester and app are fixed to make sure the unit tests are always up to date and executed prior to building the app. Added a make target named run_tests in case somebody wants to run the unit tests manually.

With this revision you will experience problems if you try to build calitko in a directory that is named other than calitko. For example, if your branch is calitko-0.5.6 and you try to run qmake you’ll get the help of qmake. The reason is that currently there are multiple pro files in the project root and qmake does nothing if it does not find a pro file with the same name as the directory. To overcome the problem do:

$ qmake -makefile calitko.pro
$ make

This problem must be solved for the next release. The only solution I can think of is put the additional pro files in another directory, like build for example. Or maybe put the app and tester projects in bin and the library project in lib. Any suggestions?

Best regards,

Peter

Peter Dimov wrote:OK guys! Here is a patch (committed in revno 73) that generates a calitko library and links the unit tests against this library. Furthermore, the calitko app is linked only if all tests pass! The tests are run as a pre build step of the app and thus the actual linking is performed only if all tests passed!

I was thinking about creating a directory 3rdParty in the project root and put all libraries (currently zlib and cppunit) there. What about the suggestion not to use the Testing subtree but rather put tests and stubs in a corresponding sub-package for each package (the suggestion in one of my previous posts)?

Regards,

Peter

Would you like to post a relpy?


This post is a reply to:
Re: Re: Re: Re: Unit Testing is vital
OK guys! Here is a patch (committed in revno 73) that generates a calitko library and links the unit tests against this library. Furthermore, the calitko app is linked only (more...)

No follow-ups yet.