code2test-support

[Code2test-support] Syncing unittests removes user added members and includes

[<sm...@1s...>]

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

Re: [Code2test-support] Syncing unittests removes user added members and includes

[Thomas F. <tfi...@cr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

Petr Smrčka wrote:
> I'm using your utility for generating unittest skeletons, it very 
> helpful. I came across to some issues which should be fixed:
great to hear that :)

> 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 
> can have for example declaration of two classess which are somehow 
> 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
sure, just give me a patch or some code and a little explanation, i will then
integrate it somehow

> 2. if I implement a test case - I add some #include lines and some 
> memeber variables to a test class, after syncing source tree and 
> tests/unittests source tree all these changes are lost. It  would be 
> great if  all manual changes stayed there forever.
this is a known issue, where i have to improve the script
i will have a look at it, to see how complex this modification can get and mail
back to this list, if i know more

> I'm really interested in using thsis utility in the future beacuse we 
> must reach 100% percent of code coverage (line) with unittesting. If 
> interested in my patches, send me some instructions and I can post them 
> to you via. mail or SVN (preffered way).
as stated above i'm interested
i do not believe that anonymous users have svn write access to the subversion
repository, so if this does not work, just send me the changed code or a patch i
could apply

thanks for your efforts!

> Thanks for an anwser (hope somebody reads this list)
thanks too,
not all sourceforge.net projects that look abandoned are so ;)

kind regards,
Thomas Fischer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBRcwnUdc/LJmW0//VAQpIJwf/eI18DxxxiFVt/xt5TY2zivV3qmPN+WSP
Vdsb5l3y+rNdvj4R+bgK7zoCOHBwTgMzIuhxOKztRpbdYohGhYfihJLJbOEUi3ll
B7flaB1/Ir0yHYMMpcVmfiwMUfykzIWafm0V3TxwdKcpO+djcCjekml/Pn4usHms
x9nxeN942lYUw89rGd9/sA9u9LnCDBNbModc0IVuJxZd1fIz6D6teCAMI6/8xrrv
EX7pSTryVoAiw+RsavpUwyPfZgjIqcG7IGKrWkODQs62E3jw8UvUtJs2mAdSqsRa
m4+9XNo2m6is9qbKeqojQ3Lq6QN1wes08riZlNN5/Zi7toJ9lmYpmg==
=Cosv
-----END PGP SIGNATURE-----