I wonder how TestCases/TestCallers are intended to be used with the TestRegistry. "Normal" TestCases register themselves automatically, but when you use several TestCallers in a TestCase you have to create a TestSuite and add the TestCallers in some constructor and then call the TestSuite in the run() method (?). It would be nice if this could be done automatically, somehow.
The examples and documentation are confusing and misleading in this aspect. According to the TestCase documentation "The test runners expect a static method suite as the entry point to get a test to run.". Why? It is not called anywhere. And, BTW, the code example in TestCase does not work, it lacks the return type.
The hierarchies example doesnt help much, as it has two constructors that get a TestSuite, but these constructors are not called anywhere. After wondering for some time how this could work a started to add prints in the TestCaller-methods and - the test methods dont even run, the example is broken.
CppUnit's concept is nice and I dont know any other good OSS testing packages, but it has cost me several hours because of the const bug (see patches), broken examples and confusing documentation. Please put together a new version with the const patch and without the broken example. If your time does not permit this I would be willing to correct the example and documentation and create a package for a new release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree with you complelty about that Cppunit is one of the best testing packages ive found, yet. But still it is so incoherent, with broken releases and examples.
I would also gladly help with correcting and perhaps adding value to this package, so a new version can be released.
So if you want help, just let us known !
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey guys, I agree completely. The only reason I don't complain is that means I should be doing it myself (that's what free software is about, right?), and I simply don't have time right now. I think a LOT of people will be greatful if this package can get sorted out.
There's a great opporutnity to fill a need here and the ball is getting dropped.
Bob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wonder how TestCases/TestCallers are intended to be used with the TestRegistry. "Normal" TestCases register themselves automatically, but when you use several TestCallers in a TestCase you have to create a TestSuite and add the TestCallers in some constructor and then call the TestSuite in the run() method (?). It would be nice if this could be done automatically, somehow.
The examples and documentation are confusing and misleading in this aspect. According to the TestCase documentation "The test runners expect a static method suite as the entry point to get a test to run.". Why? It is not called anywhere. And, BTW, the code example in TestCase does not work, it lacks the return type.
The hierarchies example doesnt help much, as it has two constructors that get a TestSuite, but these constructors are not called anywhere. After wondering for some time how this could work a started to add prints in the TestCaller-methods and - the test methods dont even run, the example is broken.
CppUnit's concept is nice and I dont know any other good OSS testing packages, but it has cost me several hours because of the const bug (see patches), broken examples and confusing documentation. Please put together a new version with the const patch and without the broken example. If your time does not permit this I would be willing to correct the example and documentation and create a package for a new release.
I agree with you complelty about that Cppunit is one of the best testing packages ive found, yet. But still it is so incoherent, with broken releases and examples.
I would also gladly help with correcting and perhaps adding value to this package, so a new version can be released.
So if you want help, just let us known !
Hey guys, I agree completely. The only reason I don't complain is that means I should be doing it myself (that's what free software is about, right?), and I simply don't have time right now. I think a LOT of people will be greatful if this package can get sorted out.
There's a great opporutnity to fill a need here and the ball is getting dropped.
Bob
Hi guys,
I am sorry that currently I can't find the time to work on cppunit. In a few weeks the following changes will be accomplished:
- const consistency
- namespace disabling via ./configure switch
- test registry removal and replacement by manual insertion (again).
I think these are the most popular demands, of course the manual should be updated.
I'm sorry for this kind of treatment of cppunit, but I have a project deadline to meet.
eric