I made several changes and added extensions based
on CppUnit version 1.5, before I learned about the sourceforge
project. In particular, I wrote a CORBA interface and layer
in the library which allows C++ tests to be browsed and run
from the JUnit test runners, including swingui.TestRunner.
It works well with JUnit 3.2, and I have only briefly tested it
JUnit 3.5. I have posted the source and a simple changes
page here in an announcement at the top of my home page:
Perhaps this is useful to someone... I do not really have time
to incorporate the changes into the current CppUnit project,
nor am I sure the changes would be considered consistent
with the current goals for CppUnit anyway. It works well as
a way to have a portable testing GUI and for running tests
across multiple hosts and architectures simultaneously.
Feel free to email me with questions, I can try to help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made several changes and added extensions based
on CppUnit version 1.5, before I learned about the sourceforge
project. In particular, I wrote a CORBA interface and layer
in the library which allows C++ tests to be browsed and run
from the JUnit test runners, including swingui.TestRunner.
It works well with JUnit 3.2, and I have only briefly tested it
JUnit 3.5. I have posted the source and a simple changes
page here in an announcement at the top of my home page:
http://www.atd.ucar.edu/~granger
Perhaps this is useful to someone... I do not really have time
to incorporate the changes into the current CppUnit project,
nor am I sure the changes would be considered consistent
with the current goals for CppUnit anyway. It works well as
a way to have a portable testing GUI and for running tests
across multiple hosts and architectures simultaneously.
Feel free to email me with questions, I can try to help.