atul wrote:…

I’m quite sure your function and similar ones can be used on other places as well so we should make sure we reuse them!

Sure… Also let me know if the function/method names are okay - ( that is a very important refactoring ) - Go the readability way ;-)

Now that you ask, maybe findCString or validateCString would be better than lenCString. Would you also please use the Calitko style of brackets spacing? I’ll write a separate post about that, in which I would like to address the style-related issues and gather some comments and opinions back. I hope I’ll manage to do the writing later tonight.

…..

Any further ideas are welcome!

I integrated CppUnit test suite with the main make file and the tests built and ran within some seconds.. However, this integration needs some thinking.. ( it is a post build step )

It gives you a safety net feeling and gets the code under an automatic scanner ;-)

Do you mean you integrated CppUnit with the main make file of Calitko? If so, please DO send me the modified Makefile along with test cases per email directly or publish them here! I really want to try that stuff out!

Regarding integration, something has to be added in calitko.pro in order to have that post build step generated in the Makefile. We’ll also need some people to write unit tests for most of the code, where applicable. We should also do some thinking about how to write tests which involve signals and slots. I guess some thinking has already been done in the community because I saw there is a QxTestRunner (Qt4 based graphics test runner) for CppUnit.