Getting up to speed quickly...
Brought to you by:
blep
Menu
▾
▴
Hello. I am new to "extreme" programming (which is what led me to this project), but I am not new to C++. I have been looking for a good unit test framework for quite sometime. I have only recently begun looking at cppunit. I must admit that my interest has been sparked. However, I am finding the execution of this unit test framework rather confusing.
There are several items which I would find extremely useful in helping a person not intimately familiar with the project spin up much more quickly and be able to apply the framework with minimal prior knowledge.
1. First and foremost, a good example. There needs to be a range of examples from trivial to more complex. And the examples must be documented and they must work.
2. Documentation. Everything from a simple HOWTO to a more complete full length document on how to effectively use (and extend) the system.
3. Keeping CVS and making better patches would help those of us trying to keep abreast of the latest developments. Plus, integrating patches into releases (and having a test release series) would help new comers.
I am willing to help with any or all of these aspects (as I really need a good unit testing framework). Please feel free to contact me and tell me how moronic I am being or better yet how I can assist.
Thanks.
Dale Hawkins
dhawkins@cdrgts.com
You're not being moronic at all. I never did get cppunit up and running. I suggest you take a look at: http://www.cuj.com/archive/1809/feature.html. Everything you need to get started is there.
Bob
to: http://www.cuj.com/articles/2000/0009/0009d/0009d.htm
Thanks for the pointer. I like the cuj. Good magazine.
-Dale
>>3. Keeping CVS and making better patches would help those of us trying to keep abreast of the latest developments. Plus, integrating patches into releases (and having a test release series) would help newcomers. <<
As you may have noticed in earlier messages the maintainers currently do not have the time to maintain it. I'm also waiting for the next revision, and if there is no usable release in the next month or so I will probably fork cppunit. ccunit is a better name anyway and as we are using the framework at work, I already maintain my own CVS repository with a number of changes and improvement (you can find most changes in the sourceforge patch section).
I did notice (and applied) some of the ccunit patches. (I had to fiddle with the patch program a bit, but such is life). I am anxious to start working on the project (including some documentation), but I have no desire to do so in isolation nor without a working cvs repository to code against.
>>but I have no desire to do so in isolation nor without a working cvs repository to code against.<<
Setting up your own CVS repository is pretty easy. Once you have imported it all you have to do to put a patch in the patch tracker is making a cvs diff.
bye...