cppunit-devel Mailing List for CppUnit - C++ port of JUnit (Page 38)
Brought to you by:
blep
Menu
▾
▴
cppunit-devel — CppUnit Developer Mailing List
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
(21) |
May
(96) |
Jun
(109) |
Jul
(42) |
Aug
(6) |
Sep
(106) |
Oct
(60) |
Nov
(20) |
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(7) |
Feb
(11) |
Mar
(49) |
Apr
(124) |
May
(30) |
Jun
(37) |
Jul
(53) |
Aug
(33) |
Sep
(21) |
Oct
(22) |
Nov
(19) |
Dec
(15) |
| 2003 |
Jan
(34) |
Feb
(25) |
Mar
(11) |
Apr
(12) |
May
(16) |
Jun
(24) |
Jul
(23) |
Aug
(23) |
Sep
(42) |
Oct
(7) |
Nov
(32) |
Dec
(33) |
| 2004 |
Jan
(41) |
Feb
(41) |
Mar
(24) |
Apr
(25) |
May
(18) |
Jun
(13) |
Jul
(11) |
Aug
(15) |
Sep
(22) |
Oct
(10) |
Nov
(15) |
Dec
(9) |
| 2005 |
Jan
(4) |
Feb
(15) |
Mar
(11) |
Apr
(16) |
May
(29) |
Jun
(17) |
Jul
(27) |
Aug
(12) |
Sep
(9) |
Oct
(10) |
Nov
(5) |
Dec
(6) |
| 2006 |
Jan
(2) |
Feb
(6) |
Mar
(7) |
Apr
(2) |
May
(1) |
Jun
(5) |
Jul
(8) |
Aug
(6) |
Sep
(10) |
Oct
(11) |
Nov
(15) |
Dec
(2) |
| 2007 |
Jan
(12) |
Feb
(22) |
Mar
(10) |
Apr
(7) |
May
(1) |
Jun
(8) |
Jul
(4) |
Aug
(1) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(7) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
|
| 2010 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Philippe L. <phi...@ca...> - 2002-04-22 22:44:16
|
I did a little bit more investigation, and if I use the following code =
in cppunitplugin.cpp (inside my ATL project). The following is just the =
define expanded.=20
#include "stdafx.h"
#include <cppunit/plugin/TestPlugIn.h>
class CppUnitTestPlugInNamedDefaultImpl : public =
CppUnit::TestPlugInDefaultImpl
{ =
=20
virtual std::string getSuiteName() =
=20
{ =
=20
return "Acuraci"; =
=20
} =
=20
};
extern "C" __declspec(dllexport) CppUnitTestPlugIn* =
cppunitTestPlugIn(void)
{ =
=20
static CppUnitTestPlugInNamedDefaultImpl plugIn; =
=20
return &plugIn; =
=20
}
=20
I receive this instead...
CppUnitPlugin.obj : error LNK2001: unresolved external symbol "public: =
virtual void __thiscall =
CppUnit::TestPlugInDefaultImpl::uninitialize(void)" =
(?uninitialize@TestPlugInDefaultImpl@CppUnit@@UAEXXZ)
CppUnitPlugin.obj : error LNK2001: unresolved external symbol "public: =
virtual class CppUnit::Test * __thiscall =
CppUnit::TestPlugInDefaultImpl::getTestSuite(void)" =
(?getTestSuite@TestPlugInDefaultImpl@CppUnit@@UAEPAVTest@2@XZ)
CppUnitPlugin.obj : error LNK2001: unresolved external symbol "public: =
virtual void __thiscall =
CppUnit::TestPlugInDefaultImpl::initialize(void)" =
(?initialize@TestPlugInDefaultImpl@CppUnit@@UAEXXZ)
CppUnitPlugin.obj : error LNK2019: unresolved external symbol =
"__declspec(dllimport) public: __thiscall =
CppUnit::TestPlugInDefaultImpl::TestPlugInDefaultImpl(void)" =
(__imp_??0TestPlugInDefaultImpl@CppUnit@@QAE@XZ) referenced in function =
"public: __thiscall =
CppUnitTestPlugInNamedDefaultImpl::CppUnitTestPlugInNamedDefaultImpl(void=
)" (??0CppUnitTestPlugInNamedDefaultImpl@@QAE@XZ)
CppUnitPlugin.obj : error LNK2019: unresolved external symbol =
"__declspec(dllimport) public: virtual __thiscall =
CppUnit::TestPlugInDefaultImpl::~TestPlugInDefaultImpl(void)" =
(__imp_??1TestPlugInDefaultImpl@CppUnit@@UAE@XZ) referenced in function =
"public: virtual __thiscall =
CppUnitTestPlugInNamedDefaultImpl::~CppUnitTestPlugInNamedDefaultImpl(voi=
d)" (??1CppUnitTestPlugInNamedDefaultImpl@@UAE@XZ)
It's not really an improvement but hopefully someone can help me get the =
latest version of cppunit to work with Visual .NET's C++ ATL projects.
Phil
> -----Original Message-----
> From: Philippe Lavoie=20
> Sent: Monday, April 22, 2002 6:24 PM
> To: Baptiste Lepilleur; cpp...@li...
> Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET
>=20
>=20
>=20
> Hi,
>=20
> I did a cvs update of cppunit and I can't get the testplugin=20
> to work for my own project. Everything compiles fine inside=20
> the examples .dsw. I can run them, life is good.
>=20
> I've defined CPPUNIT_DLL. Then, I added a cppunitplugin.cpp=20
> file with the following content
>=20
> #include <cppunit/plugin/TestPlugIn.h>
>=20
> CPPUNIT_PLUGIN_IMPLEMENT();
>=20
> // needed for an ATL project
> // note that cppunit fails if stdafx.h is included before the macro.
> #include "stdafx.h" =20
>=20
>=20
> Finally, I link with cppunitd_dll.lib. It compiles... but it returns
>=20
> Failed to load test plug-in:
> Symbol [cppunitTestPlugIn] not found in dynamic libary:Bob.dll
>=20
>=20
> This is really weird as simple_plugin works like a charm and=20
> I can't see what the missing option could be.
>=20
> Please help
>=20
> Phil
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
>=20
|
|
From: Philippe L. <phi...@ca...> - 2002-04-22 22:23:50
|
Hi, I did a cvs update of cppunit and I can't get the testplugin to work for = my own project. Everything compiles fine inside the examples .dsw. I can = run them, life is good. I've defined CPPUNIT_DLL. Then, I added a cppunitplugin.cpp file with = the following content #include <cppunit/plugin/TestPlugIn.h> CPPUNIT_PLUGIN_IMPLEMENT(); // needed for an ATL project // note that cppunit fails if stdafx.h is included before the macro. #include "stdafx.h" =20 Finally, I link with cppunitd_dll.lib. It compiles... but it returns Failed to load test plug-in: Symbol [cppunitTestPlugIn] not found in dynamic libary:Bob.dll This is really weird as simple_plugin works like a charm and I can't see = what the missing option could be. Please help Phil |
|
From: Stanley S. <su...@t-...> - 2002-04-22 19:36:53
|
Here's the latest problem: gmake[2]: Entering directory = `/space/local_users/sutton/projects/cppunit/src/DllPlugInTester' /bin/bash ../../libtool --mode=3Dlink CC -g -o DllPlugInTester -ldl = DllPlugInTester.o CommandLineParser.o ../../src/cppunit/libcppunit.la=20 CC -g -o .libs/DllPlugInTester DllPlugInTester.o CommandLineParser.o = -ldl ../../src/cppunit/.libs/libcppunit.so -R/home/sutton/solaris/lib ild: (undefined symbol) unsigned = std::deque<CppUnit::TestFailure*,std::allocator<CppUnit::TestFailure*> = >::__buffer_size() -- referenced in = ../../src/cppunit/.libs/libcppunit.so ild: (undefined symbol) = std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::iterator = std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> = >::erase(std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> = >::iterator,std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> = >::iterator) -- referenced in ../../src/cppunit/.libs/libcppunit.so (plus many, many more in the same vein) As near as I can figure, the problem is in the template instantation. I = know we've had problems with that in our code before, do to a compiler = inker bug. We use the linker option "-z now" on all of our Solaris = compiles, as well as absolute disk paths rather than relative ones to = keep from confusing the compiler/linker. However, I haven't been able = to figure out how to add the "-z now" to the linker. ".configure = --prefix-/space/local_users/sutton/solaris LD_FLAGS=3D'-z now'" didn't = seem to have any affect. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Mon 22-Apr-02 11:24 To: Stanley Sutton; cpp...@li... Cc:=09 Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem Did you follow the step indicated in Readme.CVS (and if those don't = work, did you try the lastest tar ball ?): * Unix: To generate the configure script, you need several auxiliary tools. The version numbers are minimal: later versions should also work. autoconf 2.50 - see http://www.gnu.org/directory/autoconf.html automake 1.4 - see http://www.gnu.org/directory/automake.html libtool 1.4 - see http://www.gnu.org/directory/libtool.html After checking the sources out from CVS, you need to run the script sh autogen.sh from the top-level source directory (i.e. the one containing this file). This needs only to be done once. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 5:36 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem I'm still having some problmes on Solaris 8, using the Forte 6 compiler. = I removed all my local files and got a fresh CVS snapshot. Here's there = first error: cd . && autoconf autoconf: warning: both `configure.ac' and `configure.in' are present. autoconf: warning: proceeding with `configure.ac'. configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs. LIBOBJS' I'm using GNU make, by the way, as well as the GNU versions of most of = the utilities. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Sun 21-Apr-02 08:28 To: cpp...@li... Cc: Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball New snapshot. The problem on Unix should be fixed. Thanks to all = those who helped ! KNOWN PROBLEMS: - TestPlugIn project has not been removed from the Examples workspace = (just click cancel) - Money example is missing dependency with cppunit.dsp As usal, the snapshop can be found at: http://cppunit.sourceforge.net/snapshot/ http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz New in CppUnit 1.9.6: ---------------------- - DllPlugInTester can be parametrized from command line - Two test listener plug-in examples - An 'hello world' example & getting started document : Money - Contribution: generic makefile for Borland 5.5 free compiler. - Bug fixes * DllPlugInTester: - Advanced command line to support miscellaneous listener outputer. Parameters can now be passed to test plug-in: -c --compiler Use CompilerOutputter -x --xml [filename] Use XmlOutputter (if filename is omitted, then output to cout or cerr. -s --xsl stylesheet XML style sheet for XML Outputter -e --encoding encoding XML file encoding (UTF8, shift_jis, ISO-8859-1...) -b --brief-progress Use BriefTestProgressListener (default is TextTestProgressListener) -n --no-progress Show no test progress (disable default TextTestProgressListener) -t --text Use TextOutputter -o --cout Ouputters output to cout instead of the default cerr. filename[=3D"options"] Many filenames can be specified. They are the name of the test plug-ins to load. Optional plug-ins parameters can be specified after the filename by adding '=3D'. [:testpath] Optional. Only one test path can be specified. It must be prefixed with ':'. See TestPath constructor for syntax. 'parameters' (test plug-in or XML filename, test path...) may contains spaces if double quoted. Quote may be escaped with \". Some examples of command lines: DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll CppUnitTestPlugInd.dll Will load 2 tests plug-ins (available in lib/), use the brief test progress, output the result in XML in file tests.xml and also output the result using the compiler outputter. DllPlugInTesterd_dll.exe ClockerPlugInd.dll=3D"flat" -n = CppUnitTestPlugInd.dll Will load the 2 test plug-ins, and pass the parameter string "flat" to the Clocker plug-in, disable test progress. Clocker being a test listener plug-ins (it doesn't implements any tests, it just register a TestListener), this is equivalent to say 'run all the test of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'. DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core Will run the test named "Core" (a suite in the present case ) of the test plug-in. * Documentation - New getting started documentation. Not completed yet, but probably a good complement to the current cookbook. Explore the creation of the Money example. * Examples - Money (examples/Money): the 'hello world' example. Unit tests for a simple Money class. - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp): unit tests for CommandLineParser. Not really an example, but only slightly more complex than Money. - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in that track tests and test suites running time. Parameter: "flat" for a reporting with a flattened tree. - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that dump the test tree as it run. Paramater: "flat" for a reporting with a flattened tree. - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp): CppUnit's test suite as a test plug-in. * Contribution - Contributed by project cuppa team (http://sourceforge.jp/projects/cuppa/): - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not depend on a specific CppUnit version. * Compatiblity breaks - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester command line. * Bug Fix: - DynamicLibaryManager did not report the library name when loading a a library. - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki ('cuppa' project team). - Broken build on Unix should be fixed for most (thanks to Jeffrey Morgan). Enjoy, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/ _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
|
From: Stanley S. <su...@t-...> - 2002-04-22 17:37:44
|
Yes, I'm up to date on the tools, although since I don't have root = access on my workstation, I use the --prefix on configure. Starting = over from scratch fixed that particular problem. Once again, I'm = getting: CC -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include = -I../../include -g -Wp,-MD,.deps/DynamicLibraryManager.pp -c = DynamicLibraryManager.cpp -KPIC -DPIC CC: Warning: Option -Wp,-MD,.deps/DynamicLibraryManager.pp passed to ld, = if ld is invoked, ignored otherwise "../../include/cppunit/plugin/DynamicLibraryManagerException.h", line = 28: Error: Identifier expected instead of "}". 1 Error(s) detected. This is due to the enum in the include file, which ends in a ",}", which = the Solaris compiler treats as an error. Also, the "-Wp,-MD,.deps/..." = doesn't seem to mean anything to the Solaris compiler, so the cp and the = tr both fail. If the purpose of the option is to generat dependancies, = the -xM generates a dependancy list to stdout, -xM1 generates a unique = list with the /usr/include files filtered out. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Mon 22-Apr-02 11:24 To: Stanley Sutton; cpp...@li... Cc:=09 Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem Did you follow the step indicated in Readme.CVS (and if those don't = work, did you try the lastest tar ball ?): * Unix: To generate the configure script, you need several auxiliary tools. The version numbers are minimal: later versions should also work. autoconf 2.50 - see http://www.gnu.org/directory/autoconf.html automake 1.4 - see http://www.gnu.org/directory/automake.html libtool 1.4 - see http://www.gnu.org/directory/libtool.html After checking the sources out from CVS, you need to run the script sh autogen.sh from the top-level source directory (i.e. the one containing this file). This needs only to be done once. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 5:36 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem I'm still having some problmes on Solaris 8, using the Forte 6 compiler. = I removed all my local files and got a fresh CVS snapshot. Here's there = first error: cd . && autoconf autoconf: warning: both `configure.ac' and `configure.in' are present. autoconf: warning: proceeding with `configure.ac'. configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs. LIBOBJS' I'm using GNU make, by the way, as well as the GNU versions of most of = the utilities. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Sun 21-Apr-02 08:28 To: cpp...@li... Cc: Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball New snapshot. The problem on Unix should be fixed. Thanks to all = those who helped ! KNOWN PROBLEMS: - TestPlugIn project has not been removed from the Examples workspace = (just click cancel) - Money example is missing dependency with cppunit.dsp As usal, the snapshop can be found at: http://cppunit.sourceforge.net/snapshot/ http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz New in CppUnit 1.9.6: ---------------------- - DllPlugInTester can be parametrized from command line - Two test listener plug-in examples - An 'hello world' example & getting started document : Money - Contribution: generic makefile for Borland 5.5 free compiler. - Bug fixes * DllPlugInTester: - Advanced command line to support miscellaneous listener outputer. Parameters can now be passed to test plug-in: -c --compiler Use CompilerOutputter -x --xml [filename] Use XmlOutputter (if filename is omitted, then output to cout or cerr. -s --xsl stylesheet XML style sheet for XML Outputter -e --encoding encoding XML file encoding (UTF8, shift_jis, ISO-8859-1...) -b --brief-progress Use BriefTestProgressListener (default is TextTestProgressListener) -n --no-progress Show no test progress (disable default TextTestProgressListener) -t --text Use TextOutputter -o --cout Ouputters output to cout instead of the default cerr. filename[=3D"options"] Many filenames can be specified. They are the name of the test plug-ins to load. Optional plug-ins parameters can be specified after the filename by adding '=3D'. [:testpath] Optional. Only one test path can be specified. It must be prefixed with ':'. See TestPath constructor for syntax. 'parameters' (test plug-in or XML filename, test path...) may contains spaces if double quoted. Quote may be escaped with \". Some examples of command lines: DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll CppUnitTestPlugInd.dll Will load 2 tests plug-ins (available in lib/), use the brief test progress, output the result in XML in file tests.xml and also output the result using the compiler outputter. DllPlugInTesterd_dll.exe ClockerPlugInd.dll=3D"flat" -n = CppUnitTestPlugInd.dll Will load the 2 test plug-ins, and pass the parameter string "flat" to the Clocker plug-in, disable test progress. Clocker being a test listener plug-ins (it doesn't implements any tests, it just register a TestListener), this is equivalent to say 'run all the test of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'. DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core Will run the test named "Core" (a suite in the present case ) of the test plug-in. * Documentation - New getting started documentation. Not completed yet, but probably a good complement to the current cookbook. Explore the creation of the Money example. * Examples - Money (examples/Money): the 'hello world' example. Unit tests for a simple Money class. - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp): unit tests for CommandLineParser. Not really an example, but only slightly more complex than Money. - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in that track tests and test suites running time. Parameter: "flat" for a reporting with a flattened tree. - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that dump the test tree as it run. Paramater: "flat" for a reporting with a flattened tree. - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp): CppUnit's test suite as a test plug-in. * Contribution - Contributed by project cuppa team (http://sourceforge.jp/projects/cuppa/): - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not depend on a specific CppUnit version. * Compatiblity breaks - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester command line. * Bug Fix: - DynamicLibaryManager did not report the library name when loading a a library. - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki ('cuppa' project team). - Broken build on Unix should be fixed for most (thanks to Jeffrey Morgan). Enjoy, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/ _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
|
From: Baptiste L. <gai...@fr...> - 2002-04-22 17:17:54
|
Did you follow the step indicated in Readme.CVS (and if those don't work, did you try the lastest tar ball ?): * Unix: To generate the configure script, you need several auxiliary tools. The version numbers are minimal: later versions should also work. autoconf 2.50 - see http://www.gnu.org/directory/autoconf.html automake 1.4 - see http://www.gnu.org/directory/automake.html libtool 1.4 - see http://www.gnu.org/directory/libtool.html After checking the sources out from CVS, you need to run the script sh autogen.sh from the top-level source directory (i.e. the one containing this file). This needs only to be done once. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 5:36 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem I'm still having some problmes on Solaris 8, using the Forte 6 compiler. I removed all my local files and got a fresh CVS snapshot. Here's there first error: cd . && autoconf autoconf: warning: both `configure.ac' and `configure.in' are present. autoconf: warning: proceeding with `configure.ac'. configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs. LIBOBJS' I'm using GNU make, by the way, as well as the GNU versions of most of the utilities. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Sun 21-Apr-02 08:28 To: cpp...@li... Cc: Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball New snapshot. The problem on Unix should be fixed. Thanks to all those who helped ! KNOWN PROBLEMS: - TestPlugIn project has not been removed from the Examples workspace (just click cancel) - Money example is missing dependency with cppunit.dsp As usal, the snapshop can be found at: http://cppunit.sourceforge.net/snapshot/ http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz New in CppUnit 1.9.6: ---------------------- - DllPlugInTester can be parametrized from command line - Two test listener plug-in examples - An 'hello world' example & getting started document : Money - Contribution: generic makefile for Borland 5.5 free compiler. - Bug fixes * DllPlugInTester: - Advanced command line to support miscellaneous listener outputer. Parameters can now be passed to test plug-in: -c --compiler Use CompilerOutputter -x --xml [filename] Use XmlOutputter (if filename is omitted, then output to cout or cerr. -s --xsl stylesheet XML style sheet for XML Outputter -e --encoding encoding XML file encoding (UTF8, shift_jis, ISO-8859-1...) -b --brief-progress Use BriefTestProgressListener (default is TextTestProgressListener) -n --no-progress Show no test progress (disable default TextTestProgressListener) -t --text Use TextOutputter -o --cout Ouputters output to cout instead of the default cerr. filename[="options"] Many filenames can be specified. They are the name of the test plug-ins to load. Optional plug-ins parameters can be specified after the filename by adding '='. [:testpath] Optional. Only one test path can be specified. It must be prefixed with ':'. See TestPath constructor for syntax. 'parameters' (test plug-in or XML filename, test path...) may contains spaces if double quoted. Quote may be escaped with \". Some examples of command lines: DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll CppUnitTestPlugInd.dll Will load 2 tests plug-ins (available in lib/), use the brief test progress, output the result in XML in file tests.xml and also output the result using the compiler outputter. DllPlugInTesterd_dll.exe ClockerPlugInd.dll="flat" -n CppUnitTestPlugInd.dll Will load the 2 test plug-ins, and pass the parameter string "flat" to the Clocker plug-in, disable test progress. Clocker being a test listener plug-ins (it doesn't implements any tests, it just register a TestListener), this is equivalent to say 'run all the test of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'. DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core Will run the test named "Core" (a suite in the present case ) of the test plug-in. * Documentation - New getting started documentation. Not completed yet, but probably a good complement to the current cookbook. Explore the creation of the Money example. * Examples - Money (examples/Money): the 'hello world' example. Unit tests for a simple Money class. - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp): unit tests for CommandLineParser. Not really an example, but only slightly more complex than Money. - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in that track tests and test suites running time. Parameter: "flat" for a reporting with a flattened tree. - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that dump the test tree as it run. Paramater: "flat" for a reporting with a flattened tree. - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp): CppUnit's test suite as a test plug-in. * Contribution - Contributed by project cuppa team (http://sourceforge.jp/projects/cuppa/): - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not depend on a specific CppUnit version. * Compatiblity breaks - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester command line. * Bug Fix: - DynamicLibaryManager did not report the library name when loading a a library. - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki ('cuppa' project team). - Broken build on Unix should be fixed for most (thanks to Jeffrey Morgan). Enjoy, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/ _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
|
From: Stanley S. <su...@t-...> - 2002-04-22 17:15:27
|
Hmm, let me delete EVERYTHING and start over from loggin in. I'm not = sure why, but I've had some very strange behaviors from CVS before, like = recursive directories with GAIM. We use CVS everyday for our own = projects, and we're spread out over 3 continents without any problems, = but we use it a little differently (such as locking a module, and = "moving" it's access tokens to a local server before doing commits). -----Original Message----- From: Steve M. Robbins [mailto:ste...@vi...] Sent: Mon 22-Apr-02 11:06 To: Stanley Sutton Cc: CppUnit Development Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem On Mon, Apr 22, 2002 at 10:36:59AM -0500, Stanley Sutton wrote: >=20 > I'm still having some problmes on Solaris 8, using the Forte 6 = compiler. I > removed all my local files and got a fresh CVS snapshot. Here's there = first > error: >=20 > cd . && autoconf > autoconf: warning: both `configure.ac' and `configure.in' are present. > autoconf: warning: proceeding with `configure.ac'. ??? How did that happen? I just ran "cvs update" and there is only configure.in here. > configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ > (see section `AC_LIBOBJ vs. LIBOBJS' Neither is there any "LIBOBJ" in my configure.in. =20 Something is fishy. -S --=20 by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants |
|
From: Steve M. R. <ste...@vi...> - 2002-04-22 16:06:25
|
On Mon, Apr 22, 2002 at 10:36:59AM -0500, Stanley Sutton wrote: > > I'm still having some problmes on Solaris 8, using the Forte 6 compiler. I > removed all my local files and got a fresh CVS snapshot. Here's there first > error: > > cd . && autoconf > autoconf: warning: both `configure.ac' and `configure.in' are present. > autoconf: warning: proceeding with `configure.ac'. ??? How did that happen? I just ran "cvs update" and there is only configure.in here. > configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ > (see section `AC_LIBOBJ vs. LIBOBJS' Neither is there any "LIBOBJ" in my configure.in. Something is fishy. -S -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants |
|
From: Baptiste L. <gai...@fr...> - 2002-04-22 16:02:44
|
----- Original Message ----- From: "Michel Armin" <Arm...@si...> To: "CppUnit-Devel (E-mail)" <cpp...@li...> Sent: Monday, April 22, 2002 11:11 AM Subject: [Cppunit-devel] Some Questions > Hi all. > > Since the last time I had a look at the CppUnit project (v1.6.2), very much > has changed. Therefore I had a look at the sources this weekend. While > looking through the code, some questions came to my mind. I hope you can > help me out here: > > 1. CppUnit::Test > Why are the find-related methods not const? Shouldn't they? I feel const > find-methods are somewhat more intuitive, aren't they? They all store the test in a TestPath, which store non const pointer on the traversed test, or returns a non const pointer on a test. Since TestPath is mainly used to run test (non const) method, it makes sense (at least I beleive so). Let's me know if you have another point of view on the suggest. At first I wanted those methods to be const too. > > 2. CppUnit::TestDecorator > This class doesn't delegate _all_ the methods. IMHO, in order to have a > completely transparent Decorator, it really should delegate all methods. > What do you think of this? I guess that makes sense. At the current time, it delegates all the virtual pure method. Though I haven't found much use for that class yet (I used it for the first time in the first 'writing' of DllPlugInTester were I need to pass Test to the TestRunner without them being destroyed after the run). > 3. CppUnit::TestCase > Maybe we can enhance the run() method, so that it can also properly (with > SourceLine information) catch failures in both setUp() and tearDown()? To you means catching possible assertions made in setUp()/tearDown() ? We don't have the SourceLine information for other exception. > > 4. CppUnit::TestSuite > There is an unused m_name in this class (CppUnit::TestComposite already > defines this member; and actually uses it ;-)). Let's remove that unused > member? Removed it. Left over of when I pulled up those into TestComposite. > 5. CppUnit::TestRunner > Neither CppUnit::TextUi::TestRunner nor the MFC-based TestRunner reuses the > generic TestRunner in some way. Is that intended? Or are there some > refactorings pending? Just wondering... TextUi can be derived from CppUnit::TestRunner (only some default listener and outputter are added). The Mfc TestRunner could be derived too, it use a similar 'test' suite management for added test, but the run() method does not have anything in comon (does not take a TestResult, or a test path)? Plus the test can be run many times... I don't really know what to do with that one. > I could do (2.) - (4.) my own and submit the changes; I just don't know how > to best submit these changes. (I don't have cvs-access here :-(.) Fixed. You should have CVS access now. > > Regards > > Armin > > _______________________________________________ > Cppunit-devel mailing list > Cpp...@li... > https://lists.sourceforge.net/lists/listinfo/cppunit-devel > |
|
From: Stanley S. <su...@t-...> - 2002-04-22 15:36:20
|
I'm still having some problmes on Solaris 8, using the Forte 6 compiler. =
I removed all my local files and got a fresh CVS snapshot. Here's =
there first error:
cd . && autoconf
autoconf: warning: both `configure.ac' and `configure.in' are present.
autoconf: warning: proceeding with `configure.ac'.
configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see =
section `AC_LIBOBJ vs. LIBOBJS'
I'm using GNU make, by the way, as well as the GNU versions of most of =
the utilities.
-----Original Message-----
From: Baptiste Lepilleur [mailto:gai...@fr...]
Sent: Sun 21-Apr-02 08:28
To: cpp...@li...
Cc:=09
Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball
New snapshot. The problem on Unix should be fixed. Thanks to all =
those
who helped !
KNOWN PROBLEMS:
- TestPlugIn project has not been removed from the Examples workspace =
(just
click cancel)
- Money example is missing dependency with cppunit.dsp
As usal, the snapshop can be found at:
http://cppunit.sourceforge.net/snapshot/
http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz
http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz
New in CppUnit 1.9.6:
----------------------
- DllPlugInTester can be parametrized from command line
- Two test listener plug-in examples
- An 'hello world' example & getting started document : Money
- Contribution: generic makefile for Borland 5.5 free compiler.
- Bug fixes
* DllPlugInTester:
- Advanced command line to support miscellaneous listener outputer.
Parameters can now be passed to test plug-in:
-c --compiler
Use CompilerOutputter
-x --xml [filename]
Use XmlOutputter (if filename is omitted, then output to cout or
cerr.
-s --xsl stylesheet
XML style sheet for XML Outputter
-e --encoding encoding
XML file encoding (UTF8, shift_jis, ISO-8859-1...)
-b --brief-progress
Use BriefTestProgressListener (default is TextTestProgressListener)
-n --no-progress
Show no test progress (disable default TextTestProgressListener)
-t --text
Use TextOutputter
-o --cout
Ouputters output to cout instead of the default cerr.
filename[=3D"options"]
Many filenames can be specified. They are the name of the
test plug-ins to load. Optional plug-ins parameters can be
specified after the filename by adding '=3D'.
[:testpath]
Optional. Only one test path can be specified. It must
be prefixed with ':'. See TestPath constructor for syntax.
'parameters' (test plug-in or XML filename, test path...) may contains
spaces if double quoted. Quote may be escaped with \".
Some examples of command lines:
DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll
CppUnitTestPlugInd.dll
Will load 2 tests plug-ins (available in lib/), use the brief test
progress, output the result in XML in file tests.xml and also
output the result using the compiler outputter.
DllPlugInTesterd_dll.exe ClockerPlugInd.dll=3D"flat" -n =
CppUnitTestPlugInd.dll
Will load the 2 test plug-ins, and pass the parameter string "flat"
to the Clocker plug-in, disable test progress. Clocker being a test
listener plug-ins (it doesn't implements any tests, it just register
a TestListener), this is equivalent to say 'run all the test
of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'.
DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core
Will run the test named "Core" (a suite in the present case ) of the
test plug-in.
* Documentation
- New getting started documentation. Not completed yet, but probably
a good complement to the current cookbook. Explore the creation
of the Money example.
* Examples
- Money (examples/Money): the 'hello world' example. Unit tests for
a simple Money class.
- DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp):
unit tests for CommandLineParser. Not really an example, but only
slightly more complex than Money.
- ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in
that track tests and test suites running time. Parameter: "flat"
for a reporting with a flattened tree.
- DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that
dump the test tree as it run. Paramater: "flat" for a reporting
with a flattened tree.
- CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp):
CppUnit's test suite as a test plug-in.
* Contribution
- Contributed by project cuppa team
(http://sourceforge.jp/projects/cuppa/):
- Makefile for CppUnit with Borland C++ 5.5 free compiler: does not
depend on a specific CppUnit version.
* Compatiblity breaks
- DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester
command line.
* Bug Fix:
- DynamicLibaryManager did not report the library name when loading a
a library.
- BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki
('cuppa' project team).
- Broken build on Unix should be fixed for most (thanks to
Jeffrey Morgan).
Enjoy,
Baptiste.
---
Baptiste Lepilleur <gai...@fr...>
http://gaiacrtn.free.fr/
_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel
|
|
From: Michel A. <Arm...@si...> - 2002-04-22 09:11:14
|
Hi all. Since the last time I had a look at the CppUnit project (v1.6.2), very much has changed. Therefore I had a look at the sources this weekend. While looking through the code, some questions came to my mind. I hope you can help me out here: 1. CppUnit::Test Why are the find-related methods not const? Shouldn't they? I feel const find-methods are somewhat more intuitive, aren't they? 2. CppUnit::TestDecorator This class doesn't delegate _all_ the methods. IMHO, in order to have a completely transparent Decorator, it really should delegate all methods. What do you think of this? 3. CppUnit::TestCase Maybe we can enhance the run() method, so that it can also properly (with SourceLine information) catch failures in both setUp() and tearDown()? 4. CppUnit::TestSuite There is an unused m_name in this class (CppUnit::TestComposite already defines this member; and actually uses it ;-)). Let's remove that unused member? 5. CppUnit::TestRunner Neither CppUnit::TextUi::TestRunner nor the MFC-based TestRunner reuses the generic TestRunner in some way. Is that intended? Or are there some refactorings pending? Just wondering... I could do (2.) - (4.) my own and submit the changes; I just don't know how to best submit these changes. (I don't have cvs-access here :-(.) Regards Armin |
|
From: Benjabette E. <ben...@ya...> - 2002-04-22 06:03:09
|
Hi! I have been investigating cppunit for quite some time now. I just want to know if it can be integrated or used in MFC-based applications(in VC++ 6.0). If so, can you give a simple example or steps in testing the UI components of a dialog-based application. Thank you in advance. -benjabette =) __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ |
|
From: Baptiste L. <gai...@fr...> - 2002-04-21 14:06:30
|
New snapshot. The problem on Unix should be fixed. Thanks to all those
who helped !
KNOWN PROBLEMS:
- TestPlugIn project has not been removed from the Examples workspace (just
click cancel)
- Money example is missing dependency with cppunit.dsp
As usal, the snapshop can be found at:
http://cppunit.sourceforge.net/snapshot/
http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz
http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz
New in CppUnit 1.9.6:
----------------------
- DllPlugInTester can be parametrized from command line
- Two test listener plug-in examples
- An 'hello world' example & getting started document : Money
- Contribution: generic makefile for Borland 5.5 free compiler.
- Bug fixes
* DllPlugInTester:
- Advanced command line to support miscellaneous listener outputer.
Parameters can now be passed to test plug-in:
-c --compiler
Use CompilerOutputter
-x --xml [filename]
Use XmlOutputter (if filename is omitted, then output to cout or
cerr.
-s --xsl stylesheet
XML style sheet for XML Outputter
-e --encoding encoding
XML file encoding (UTF8, shift_jis, ISO-8859-1...)
-b --brief-progress
Use BriefTestProgressListener (default is TextTestProgressListener)
-n --no-progress
Show no test progress (disable default TextTestProgressListener)
-t --text
Use TextOutputter
-o --cout
Ouputters output to cout instead of the default cerr.
filename[="options"]
Many filenames can be specified. They are the name of the
test plug-ins to load. Optional plug-ins parameters can be
specified after the filename by adding '='.
[:testpath]
Optional. Only one test path can be specified. It must
be prefixed with ':'. See TestPath constructor for syntax.
'parameters' (test plug-in or XML filename, test path...) may contains
spaces if double quoted. Quote may be escaped with \".
Some examples of command lines:
DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll
CppUnitTestPlugInd.dll
Will load 2 tests plug-ins (available in lib/), use the brief test
progress, output the result in XML in file tests.xml and also
output the result using the compiler outputter.
DllPlugInTesterd_dll.exe ClockerPlugInd.dll="flat" -n CppUnitTestPlugInd.dll
Will load the 2 test plug-ins, and pass the parameter string "flat"
to the Clocker plug-in, disable test progress. Clocker being a test
listener plug-ins (it doesn't implements any tests, it just register
a TestListener), this is equivalent to say 'run all the test
of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'.
DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core
Will run the test named "Core" (a suite in the present case ) of the
test plug-in.
* Documentation
- New getting started documentation. Not completed yet, but probably
a good complement to the current cookbook. Explore the creation
of the Money example.
* Examples
- Money (examples/Money): the 'hello world' example. Unit tests for
a simple Money class.
- DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp):
unit tests for CommandLineParser. Not really an example, but only
slightly more complex than Money.
- ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in
that track tests and test suites running time. Parameter: "flat"
for a reporting with a flattened tree.
- DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that
dump the test tree as it run. Paramater: "flat" for a reporting
with a flattened tree.
- CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp):
CppUnit's test suite as a test plug-in.
* Contribution
- Contributed by project cuppa team
(http://sourceforge.jp/projects/cuppa/):
- Makefile for CppUnit with Borland C++ 5.5 free compiler: does not
depend on a specific CppUnit version.
* Compatiblity breaks
- DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester
command line.
* Bug Fix:
- DynamicLibaryManager did not report the library name when loading a
a library.
- BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki
('cuppa' project team).
- Broken build on Unix should be fixed for most (thanks to
Jeffrey Morgan).
Enjoy,
Baptiste.
---
Baptiste Lepilleur <gai...@fr...>
http://gaiacrtn.free.fr/
|
|
From: Baptiste L. <gai...@fr...> - 2002-04-21 12:30:26
|
I had already fixed the make check problem (once you get the gist of it, it was not that difficult). I integrated the 'new lines' patches. Thanks Jeffrey, Baptiste. ----- Original Message ----- From: "Jeffrey Morgan" <ku...@zo...> To: <cpp...@li...> Sent: Sunday, April 21, 2002 3:09 AM Subject: Re: [Cppunit-devel] possible problem with build 1.9.4 > Attached is another patch that will allow 'make check' to compile > correctly. Please apply it after the previous patch I sent. > > -Jeff > > > > > > Attached is a simple patch that fixes the build problem on Linux. > > > > I just tried it and it works great. Thanks again! > > > > > > > |
|
From: Jeffrey M. <ku...@zo...> - 2002-04-21 01:09:47
|
Attached is another patch that will allow 'make check' to compile correctly. Please apply it after the previous patch I sent. -Jeff > > > Attached is a simple patch that fixes the build problem on Linux. > > I just tried it and it works great. Thanks again! > > |
|
From: Jeffrey M. <ku...@zo...> - 2002-04-21 00:53:52
|
> > < #endif > \ No newline at end of file > --- > > #endif > > > > => means that a new line should be added to the file, right ? Yes. The gnu compiler complains with a warning if the newline is not there. > > Well, you're patch should fix the problem for most, dl.so is present on most > (all?) Unix, isn't it ? I believe it should be available on almost all open systems. A more precise approach would be to check for it and setup accordingly. |
|
From: Jeffrey M. <ku...@zo...> - 2002-04-21 00:50:25
|
On Sat, 2002-04-20 at 17:04, Baptiste Lepilleur wrote: > Thanks !!! > > I'll integrate this and keep you posted. > > < #endif > \ No newline at end of file > --- > > #endif > > > > => means that a new line should be added to the file, right ? > > Well, you're patch should fix the problem for most, dl.so is present on most > (all?) Unix, isn't it ? > > Baptiste. > > ----- Original Message ----- > From: "Jeffrey Morgan" <ku...@zo...> > To: <cpp...@li...> > Sent: Saturday, April 20, 2002 6:54 PM > Subject: Re: [Cppunit-devel] possible problem with build 1.9.4 > > > > Attached is a simple patch that fixes the build problem on Linux. > > It doesn't contain the check for --disable-test-plug-in and > > conditional compilation of the plugin example. If I have the > > time over the next couple of days I will try to add this as well. > > This patch also adds a newline to the end of a couple of files to > > keep an annoying warning from displaying when compiling with the > > gnu compiler. > > > > -Jeff > > > > On Sat, 2002-04-20 at 05:38, Baptiste Lepilleur wrote: > > > I think I finally got what this problem is related to. I used 'make > dist' to > > > make this distribution (since the build on Unix is broken (see NEWS) I > got > > > use 'make distcheck'). It seems that build rule does not works. > > > > > > The best I could do if somebody want to tackle the Unix build problem > and > > > does not have CVS access it a tar ball of the exported CVS. > > > > > > Baptiste. > > > > > > ----- Original Message ----- > > > From: "Jeffrey Morgan" <ku...@zo...> > > > To: <cpp...@li...> > > > Sent: Saturday, April 20, 2002 2:36 AM > > > Subject: [Cppunit-devel] possible problem with build 1.9.4 > > > > > > > > > > I just downloaded version 1.9.4 but when I tried to compile > > > > on rh 7.2 I got an error due to the fact that the file > > > > config/depcomp didn't exist. I checked and this file was in > > > > the 1.8.0 build. If I copy this file from the 1.8.0 build > > > > into the config directory of the 1.9.4 build it compiles > > > > without problem. > > > > > > > > -Jeff > > > > > > > > > > > > _______________________________________________ > > > > Cppunit-devel mailing list > > > > Cpp...@li... > > > > https://lists.sourceforge.net/lists/listinfo/cppunit-devel > > > > > > > > > > > > > > > > |
|
From: Baptiste L. <gai...@fr...> - 2002-04-20 22:33:18
|
----- Original Message ----- From: "Jeffrey Morgan" <ku...@zo...> To: <cpp...@li...> Sent: Saturday, April 20, 2002 6:54 PM Subject: Re: [Cppunit-devel] possible problem with build 1.9.4 > Attached is a simple patch that fixes the build problem on Linux. I just tried it and it works great. Thanks again! > It doesn't contain the check for --disable-test-plug-in and That would be useful. I just got a patch for BeOS and that option would help. I'll try to make another snapshot by tomorrow. Baptiste. > conditional compilation of the plugin example. If I have the > time over the next couple of days I will try to add this as well. > This patch also adds a newline to the end of a couple of files to > keep an annoying warning from displaying when compiling with the > gnu compiler. > > -Jeff |
|
From: Baptiste L. <gai...@fr...> - 2002-04-20 20:56:51
|
Thanks !!! I'll integrate this and keep you posted. < #endif \ No newline at end of file --- > #endif > => means that a new line should be added to the file, right ? Well, you're patch should fix the problem for most, dl.so is present on most (all?) Unix, isn't it ? Baptiste. ----- Original Message ----- From: "Jeffrey Morgan" <ku...@zo...> To: <cpp...@li...> Sent: Saturday, April 20, 2002 6:54 PM Subject: Re: [Cppunit-devel] possible problem with build 1.9.4 > Attached is a simple patch that fixes the build problem on Linux. > It doesn't contain the check for --disable-test-plug-in and > conditional compilation of the plugin example. If I have the > time over the next couple of days I will try to add this as well. > This patch also adds a newline to the end of a couple of files to > keep an annoying warning from displaying when compiling with the > gnu compiler. > > -Jeff > > On Sat, 2002-04-20 at 05:38, Baptiste Lepilleur wrote: > > I think I finally got what this problem is related to. I used 'make dist' to > > make this distribution (since the build on Unix is broken (see NEWS) I got > > use 'make distcheck'). It seems that build rule does not works. > > > > The best I could do if somebody want to tackle the Unix build problem and > > does not have CVS access it a tar ball of the exported CVS. > > > > Baptiste. > > > > ----- Original Message ----- > > From: "Jeffrey Morgan" <ku...@zo...> > > To: <cpp...@li...> > > Sent: Saturday, April 20, 2002 2:36 AM > > Subject: [Cppunit-devel] possible problem with build 1.9.4 > > > > > > > I just downloaded version 1.9.4 but when I tried to compile > > > on rh 7.2 I got an error due to the fact that the file > > > config/depcomp didn't exist. I checked and this file was in > > > the 1.8.0 build. If I copy this file from the 1.8.0 build > > > into the config directory of the 1.9.4 build it compiles > > > without problem. > > > > > > -Jeff > > > > > > > > > _______________________________________________ > > > Cppunit-devel mailing list > > > Cpp...@li... > > > https://lists.sourceforge.net/lists/listinfo/cppunit-devel > > > > > > > > > |
|
From: Jeffrey M. <ku...@zo...> - 2002-04-20 16:54:14
|
Attached is a simple patch that fixes the build problem on Linux. It doesn't contain the check for --disable-test-plug-in and conditional compilation of the plugin example. If I have the time over the next couple of days I will try to add this as well. This patch also adds a newline to the end of a couple of files to keep an annoying warning from displaying when compiling with the gnu compiler. -Jeff On Sat, 2002-04-20 at 05:38, Baptiste Lepilleur wrote: > I think I finally got what this problem is related to. I used 'make dist' to > make this distribution (since the build on Unix is broken (see NEWS) I got > use 'make distcheck'). It seems that build rule does not works. > > The best I could do if somebody want to tackle the Unix build problem and > does not have CVS access it a tar ball of the exported CVS. > > Baptiste. > > ----- Original Message ----- > From: "Jeffrey Morgan" <ku...@zo...> > To: <cpp...@li...> > Sent: Saturday, April 20, 2002 2:36 AM > Subject: [Cppunit-devel] possible problem with build 1.9.4 > > > > I just downloaded version 1.9.4 but when I tried to compile > > on rh 7.2 I got an error due to the fact that the file > > config/depcomp didn't exist. I checked and this file was in > > the 1.8.0 build. If I copy this file from the 1.8.0 build > > into the config directory of the 1.9.4 build it compiles > > without problem. > > > > -Jeff > > > > > > _______________________________________________ > > Cppunit-devel mailing list > > Cpp...@li... > > https://lists.sourceforge.net/lists/listinfo/cppunit-devel > > > > |
|
From: Baptiste L. <gai...@fr...> - 2002-04-20 10:22:05
|
I think I finally got what this problem is related to. I used 'make dist' to make this distribution (since the build on Unix is broken (see NEWS) I got use 'make distcheck'). It seems that build rule does not works. The best I could do if somebody want to tackle the Unix build problem and does not have CVS access it a tar ball of the exported CVS. Baptiste. ----- Original Message ----- From: "Jeffrey Morgan" <ku...@zo...> To: <cpp...@li...> Sent: Saturday, April 20, 2002 2:36 AM Subject: [Cppunit-devel] possible problem with build 1.9.4 > I just downloaded version 1.9.4 but when I tried to compile > on rh 7.2 I got an error due to the fact that the file > config/depcomp didn't exist. I checked and this file was in > the 1.8.0 build. If I copy this file from the 1.8.0 build > into the config directory of the 1.9.4 build it compiles > without problem. > > -Jeff > > > _______________________________________________ > Cppunit-devel mailing list > Cpp...@li... > https://lists.sourceforge.net/lists/listinfo/cppunit-devel > |
|
From: Jeffrey M. <ku...@zo...> - 2002-04-20 00:36:48
|
I just downloaded version 1.9.4 but when I tried to compile on rh 7.2 I got an error due to the fact that the file config/depcomp didn't exist. I checked and this file was in the 1.8.0 build. If I copy this file from the 1.8.0 build into the config directory of the 1.9.4 build it compiles without problem. -Jeff |
|
From: Duane M. <dua...@ma...> - 2002-04-19 15:25:01
|
--- At Fri, 19 Apr 2002 12:57:53 +0200, Baptiste Lepilleur wrote:
>I did this instead (remove the ugly #ifdef):
>
>std::string
>TypeInfoHelper::getClassName( const std::type_info &info )
>{
> static std::string classPrefix( "class " );
> std::string name( info.name() );
>
> if ( name.substr( 0, classPrefix.length() ) == classPrefix )
> return name.substr( classPrefix.length() );
> return name;
>}
>
>Let me know if it's works.
>Baptiste.
>
>PS: is there any reason for comparing the size() with the length() ?
std::string::length() and std::string::size() are synonyms. length() is
commonly used for string (ie strlen) however, size() was used for
containers (vectors, etc). So they included both. This allows std::string
to be compatible with the "container interface".
>----- Original Message -----
>From: "FUKUDA Fumiki" <ff...@nt...>
>To: <cpp...@li...>
>Sent: Thursday, April 18, 2002 9:05 AM
>Subject: [Cppunit-devel] questionable code @ TypeInfoHelper.cpp
>
>
>> Hi all,
>>
>> ----- excerpt from src/cppunit/TypeInfoHelper.cpp -----
>> std::string
>> TypeInfoHelper::getClassName( const std::type_info &info )
>> {
>> static std::string classPrefix( "class " );
>> std::string name( info.name() );
>>
>> bool has_class_prefix = 0 ==
>> #if CPPUNIT_FUNC_STRING_COMPARE_STRING_FIRST
>> name.compare( classPrefix, 0, classPrefix.length() );
>> #else
>> name.compare( 0, classPrefix.length(), classPrefix );
>> #endif
>> return has_class_prefix ? name.substr( classPrefix.length() ) : name;
>> }
>> ------------------
>>
>> if info.name().length() < classPrefix.length(), an exception should be
>thrown.
>> I think this method should return 'name' at this condition (as follows).
>>
>> ...
>> static std::string classPrefix( "class " );
>> std::string name( info.name() );
>>
>> if ( name.length() < classPrefix.size() ) return name; // ADD THIS!
>>
>> bool has_class_prefix = 0 == ...
...Duane
--
"If tyranny and oppression come to this land, it will be in the
guise of fighting a foreign enemy." - James Madison
|
|
From: Baptiste L. <gai...@fr...> - 2002-04-19 15:15:39
|
A much more mature test plug-in system that makes testable component a
reality. A lot of polishon many features.
Notes that if the Unix side is fixed by the time of next public release,
the next public release might very well come with a broken unix build (there
is way to much new features to wait too long).
As usual:
http://cppunit.sourceforge.net/snapshot/
http://cppunit.sourceforge.net/snapshot/cppunit-1.9.4.tar.gz
http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.4.tar.gz
New in CppUnit 1.9.4:
----------------------
- More versatile, easier to make test plug-in.
- A PlugInManager to manage multiple test plug-ins.
- Crossplatform test plug-in runner.
- Crossplatform test plug-in example.
- A brief progress listener
- Easier test hierarchy creation
- Improved documentation.
- Tracking of test run start/end.
- Contribution: XML style sheet & borland 5.5 makefile.
- Help needed on the Unix side!
* Buildling on Unix:
- I did not get any feed back on the previous build issue on Unix. Using
a simple autobook example was useless to try to solve the problem. Here
is the issue:
CppUnit library build fine, it is the example I'm having trouble with.
Since the test plug-in have been added, CppUnit use the function
dlopen(), dlsym() and dlclose() on unix to load/unload the plug-in.
Those functions apparently requires to link another library when
building an exectuable. Here is was should be done:
- linking against the said library for each example.
- generates the shared library for the examples/simple/simple_plugin
example (source files are ExampleTestCase.cpp, ExampleTestCase.cpp
and SimplePlugIn.cpp).
- if possible, makes the above optionnal if --disable-test-plug-in
is defined:
- don't link the dlXXX library
- don't compile the plug-in example
- add #define CPPUNIT_NO_TESTPLUGIN 1 to the config file
Contact me on the mailing-list for more details.
* TestPlugIn:
- A simple fact I realised while testing: if you link your test plug-in
against the DLL version of cppunit (or shared library on Unix), then
test registered to the TestFactoryRegistry (it is what's hide behind
CPPUNIT_TEST_SUITE_REGISTRATION) are automatically shared. Changes
have been made to support that usage (CppUnit was crashing badly).
Using the TestFactoryRegistry provides much more flexiblity that
providing a single suite for the plug-in. As such:
- CppUnit plug-in should be linked against the dll version of CppUnit
library.
- Plug-in should register their tests using the CPPUNIT_TEST_SUITE_xxx
macros.
- 'homemade' suite can still be registred to the TestFactoryRegistry that
is
passed as parameter on plug-in initialization. Notes that you must
unregister those suites during plug-in uninitialization, otherwise on
destruction, the TestFactoryRegistry will attempt to destroy them... Your
plug-in would have been already unloaded...
- Plug-in can accept parameters on initialization (notes that the
Parameters
object is far from being stabilized, but whatever form it takes, it will
be
a list of string).
- Plug-in can register their one listener for a test run. This means that
you
can extends 'DllPlugInTester' by creating test plug-in... This also
means
than you can listen to startTestRun()/endTestRun() to do some global
setUp/tearDown (to initialize globales resources, such as COM...)
- Why all this fuss around test plug-in ? Test plug-in are the incarnation
of
an old concept: testable components...
* PlugInManager:
- The PlugInManager is used to load/unload plug-ins. It takes care of all
the 'plug-in' protocol and makes it easy to use multiple plug-ins at the
same time. It dispatches the addListener()/removeListener() message to
each plug-in.
* Crossplatform test plug-in runner (src/DllPlugInRunner):
- This application can be used to run your test plug-ins. It can load
multiple test plug-ins and run all or a specific test in the test
hierarchy returned by TestFactoryRegistry::getRegistry().makeTest().
- Plug-in loaded by the plug-in may also be custom TestListener.
- It can be use for post-build check and to debug the plug-in.
- Why use it? It keep you away from CppUnit API changes!
* Easier test hierarchy creation (TestFactoryRegistry/HelperMacros):
- added method addRegistry(name) to add a named registry to the registry.
see TestFactoryRegistry for an example of use.
- added macros CPPUNIT_REGISTRY_ADD( which, to ) and
CPPUNIT_REGISTRY_ADD_TO_DEFAULT( which ) to create test hierarchy at
static
initialization (in the spirit of CPPUNIT_TEST_SUITE_xxx() macros).
* VerboseTestProgressListener:
- A new TestListener that prints the test name before running it. Most
useful when
a test crashing, mean a application crash.
* Documentation:
- More details about the test plug-in, how to use it, how does it works...
See module/Writing Test Plug-in.
* Examples:
- examAdded crossplatform simple example. Equivalent to VC++ HostApp
example.
- examples/simple: a very simple example, demonstrating the use of CppUnit
with a single TestFixture. Demonstrate both how to build an application
using TestRunner, and how to build a test plug-in to use with the
test plug-in runner.
* Contribution
- Contributed by project cuppa team
(http://sourceforge.jp/projects/cuppa/):
- XML style sheet: transform CppUnit XML output into HTML.
- Makefile for CppUnit with Borland C++ 5.5 free compiler.
* Behavior changes:
- Test runner should call TestResult::runTest() to run the 'top level'
test. This
will inform the TestListener of the test run start/end.
* Compatiblity break:
- TestFactoryRegistry don't own register test anymore. AutoRegisterSuite
has
been updated to preverse its apparent behavior. It should be of concern
if you created and registered custom TestFactory.
- Removed TextTestProgressListener::done(). No longer needed, it listens
for endTestRun().
* Compatiblity Break for 1.9.2 users:
- TestPlugIn.h: CppUnitTestPlugIn as been completly rewritten.
- TestPlugIn.h: macro CPPUNIT_PLUGIN_IMPLEMENT() don't take any arguments.
- TestSuitePlugIn: removed. A similar functionnality is provided by
PlugInManager.
- TestPlugInDefaultImpl: renamed TestPlugInAdapter. It does not implements
any default behavior anymore.
- DllPlugInRunner: no longer support multiple specific tests. The test
path must
be prefixed with ':'. Release and Debug configuration links against
cppunit_dll.
* Bug Fix:
- Crash when linking CppUnit DLL within another DLL that registered test.
Caused
by the destruction of tests registered to TestFactoryRegistry. Fixed by
providing a register/unregister interface and removing the ownership of
TestFactory to TestFactoryRegistry.
Enjoy,
Baptiste.
---
Baptiste Lepilleur <gai...@fr...>
http://gaiacrtn.free.fr/
|
|
From: Baptiste L. <gai...@fr...> - 2002-04-19 14:09:25
|
The GUI version of the test plug-in is an MFC application. In TestPlugInRunnerApp::InitInstance(), you can add: CCommandLineInfo info; ParseCommandLine( info ); => you need to subclass CComandLineInfo to do your custom parsing. Baptiste. ----- Original Message ----- From: "Philippe Lavoie" <phi...@ca...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Thursday, April 18, 2002 3:33 PM Subject: RE: [Cppunit-devel] What are the command line arguments for TestPluginRunner? Can it be added to your 'oh so small' todo list ? ;) Phil PS Or point me toward a winmain of some kind and all modify it for ya :) I couldn't find the winmain, that's why I didn't do it in the first place... > -----Original Message----- > From: Baptiste Lepilleur [mailto:gai...@fr...] > Sent: Wednesday, April 17, 2002 10:15 AM > To: cpp...@li... > Subject: Re: [Cppunit-devel] What are the command line arguments for > TestPluginRunner? > > > You should use DllTestPlugInTester. TestPlugInRunner don't > take any command > line arguments. > > Baptiste. > > > ----- Original Message ----- > From: "Philippe Lavoie" <phi...@ca...> > To: <cpp...@li...> > Sent: Tuesday, April 16, 2002 12:21 AM > Subject: [Cppunit-devel] What are the command line arguments for > TestPluginRunner? > > > Hi, > > I'd like to add cppunit to the tools/external tools menu. > > I did > > Program: TestPluginRunner.exe > Arguments: $(TargetPath) > InitialDir: $(TargetDir) > > where $(TargetPath) is the full qualifed name of the output dll. > > What I was expecting was to have my dll preloaded with the > root test node > selected. Can somebody tell me if what I'm doing is feasible ? > > Thanks > > Phil > > _______________________________________________ > Cppunit-devel mailing list > Cpp...@li... > https://lists.sourceforge.net/lists/listinfo/cppunit-devel > > > > _______________________________________________ > Cppunit-devel mailing list > Cpp...@li... > https://lists.sourceforge.net/lists/listinfo/cppunit-devel > |
|
From: Baptiste L. <gai...@fr...> - 2002-04-19 10:51:47
|
I did this instead (remove the ugly #ifdef):
std::string
TypeInfoHelper::getClassName( const std::type_info &info )
{
static std::string classPrefix( "class " );
std::string name( info.name() );
if ( name.substr( 0, classPrefix.length() ) == classPrefix )
return name.substr( classPrefix.length() );
return name;
}
Let me know if it's works.
Baptiste.
PS: is there any reason for comparing the size() with the length() ?
----- Original Message -----
From: "FUKUDA Fumiki" <ff...@nt...>
To: <cpp...@li...>
Sent: Thursday, April 18, 2002 9:05 AM
Subject: [Cppunit-devel] questionable code @ TypeInfoHelper.cpp
> Hi all,
>
> ----- excerpt from src/cppunit/TypeInfoHelper.cpp -----
> std::string
> TypeInfoHelper::getClassName( const std::type_info &info )
> {
> static std::string classPrefix( "class " );
> std::string name( info.name() );
>
> bool has_class_prefix = 0 ==
> #if CPPUNIT_FUNC_STRING_COMPARE_STRING_FIRST
> name.compare( classPrefix, 0, classPrefix.length() );
> #else
> name.compare( 0, classPrefix.length(), classPrefix );
> #endif
> return has_class_prefix ? name.substr( classPrefix.length() ) : name;
> }
> ------------------
>
> if info.name().length() < classPrefix.length(), an exception should be
thrown.
> I think this method should return 'name' at this condition (as follows).
>
> ...
> static std::string classPrefix( "class " );
> std::string name( info.name() );
>
> if ( name.length() < classPrefix.size() ) return name; // ADD THIS!
>
> bool has_class_prefix = 0 == ...
>
> -----:-----:-----:-----:-----:-----:-----:-----:-----:-----
> FUKUDA (episteme) Fumiki -- magical, but never a magic...
>
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
>
|
180 messages has been excluded from this view by a project administrator.
