From: <sm...@1s...> - 2007-02-09 07:33:38
|
Hi, I'm using your utility for generating unittest skeletons, it very=20 helpful. I came across to some issues which should be fixed: 1. I know that it's a good manner to have only one class declaration per = header file (but the world is not like this ;) ), but in our project we=20 can have for example declaration of two classess which are somehow=20 logically connected and declarion of theirs container class. So I put a = little effort and changed the utility to be able to cope with it - maybe = it could be made optinal 2. if I implement a test case - I add some #include lines and some=20 memeber variables to a test class, after syncing source tree and=20 tests/unittests source tree all these changes are lost. It would be=20 great if all manual changes stayed there forever. I'm really interested in using thsis utility in the future beacuse we=20 must reach 100% percent of code coverage (line) with unittesting. If=20 interested in my patches, send me some instructions and I can post them=20 to you via. mail or SVN (preffered way). Thanks for an anwser (hope somebody reads this list) --=20 /*Petr Smr=C4=8Dka */ *Prvn=C3=AD Sign=C3=A1ln=C3=AD, a.s. * n=C3=A1m.Republiky 21 =C5=BD=C4=8F=C3=A1r nad S=C3=A1zavou 591 01 ______________________ tel: +420 566 621 459 fax: +420 566 621 465 e-mail: sm...@1s... web: www.1sig.cz Skype: smrcka ICQ: 327-017-163 |