cppunit-devel Mailing List for CppUnit - C++ port of JUnit
Brought to you by:
blep
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: CppUnit d. m. l. <cpp...@li...> - 2014-03-28 20:26:06
|
Hello CppUnit Developers, My Source Forge account is redhotdancer34 (alias CPlusPlus OOA and D). I am about ready to post via the CppUnit Tickets | Patches area, multiple files for compiling CppUnit with the more recent C++Builder compilers (e.g. Win32, Win64, and Mac OS X). I would like to know the best source file to use for a patch that is a general information readme addressing C++Builder compiling and using CppUnit within C++Builder. I have named the new file: readme_CPlusPlusBuilder_en.txt Within this file is a long list of guidance, besides the summary area at the top with File, Purpose, Author, and References sections. The length of this new file is similar to the CodingGuideLines.txt, but much different content. Is there a better text file within the CppUnit source to generate the patch? The rest of the new and updated files have existing reference source to generate patches from the /contrib/bc5/bcc-makefile.zip. I have planned to post complete patches for each compiler type at my disposal: Win32 (bcc32.exe), Win64 (bcc64.exe) and Mac OS X (bccosx.exe). The patch file names are: mksrclist.cpp makefile cppunit.mak readme_compilerExeName_en.txt where the compilerExeName is one of "bcc32", "bcc64", "bccosx," three separate files. In the case of the 64-bit version of the mksrclist.cpp, it is possible to rename this file version to mkscrlist64.cpp, right? The reason I ask is because the implementation is a bit different to support the ".o" object file extension used by the Win64 compiler (e.g. bcc64 is based on CLang 3.1). Is it preferred to have three indpendent posts, one for each compiler? Ultimately, there can easily be a whole new zip file that is called something like: ecppb-makefile.zip Then within that zip are the dedicated sub-directories for the bcc32, bcc64, and bccosx compilers. What is the preferred method to post a new zip file? Thank you all for your time and attention. Sincerely, Robert Source Forge: redhotdancer34 alias CPlusPlus OOA and D https://sourceforge.net/u/redhotdancer34/profile Stack Overflow - CPlusPlus OOA and D http://stackoverflow.com/users/3316922/cplusplus-ooa-and-d |
From: CppUnit d. m. l. <cpp...@li...> - 2014-02-18 11:51:15
|
Hi all, I've saw some activity in the commit log last year, after years of silence. Here's to hoping somebody is listening :-) We're using cppunit extensively with a large code base, and we're mostly happy with it. One thing we'd like to improve though, is crash and exception reporting on Windows. I've experimented with a structured exception filter to write out a minidump (the Windows equivalent of a core dump), and it seems to work well. So well, in fact, that I wonder if it should be our default policy even for unknown C++ exception. Unfortunately, since DefaultProtector catches (...), I never get a chance to handle them, they're just logged as: ##Failure Location unknown## : Error Test name: Test::TestAnyRandomException uncaught exception of unknown type which isn't very useful. I'd like to propose splitting DefaultProtector into three individual classes along the three catch clauses: 1) cppunit::Exception: these should be handled and reported as failures 2) std::exception: these are almost ubiquitous and should probably continue to be reported as errors (though it might be nice to make it opt-out) 3) (...): for any unknown exceptions it makes more sense (to me, anyway) to let it slip and give a debugger a chance to extract context. Of course, this imposes a soft requirement for people to write a custom protector for their custom exception types not derived from std::exception (we have one) if they want to prevent their tests from crashing hard. Thoughts? Would you take patches to demonstrate what I mean in more detail? Thanks, - Kim |
From: CppUnit d. m. l. <cpp...@li...> - 2012-08-21 06:40:07
|
Hi, My project fails to build on the latest version of Mac OS with -Wall -W -Wformat -Werror enabled due to unused variables in the 1.12.1 version of extensions/ExceptionTestCaseDecorator.h. The svn code builds correctly, so I'd like to request a release. I can update the Mac port file once the tarball is available. Thanks, Simon |
From: CppUnit d. m. l. <cpp...@li...> - 2010-01-27 18:06:27
|
Hi, On the page: http://cppunit.sourceforge.net/doc/1.11.6/money_example.html section "Our first tests", I don't see the difference between: public: Money(double amount, std::string currency ) : m_amount( amount ) , m_currency( currency ) { } supposed to be bugged, and: Money(double amount, std::string currency ) : m_amount( amount ) , m_currency( currency ) { } supposed to be fixed. Maybe the "bugged version" missed to be bugged ;-) Proposal: remove the initialization of either "m_amount" or "m_currency" in the first version, for the unit test to fail. Regards, David TYLSKI |
From: CppUnit d. m. l. <cpp...@li...> - 2009-11-25 12:50:24
|
Hi, I'd successfully Installed the 1.12.1 in cygwin, but get error when using it. Many undefined references when a program is linking to the libcppunit.a: My sanity check is: $ cppunit-config --libs -L/usr/local/lib -lcppunit -ldl And, the errors are: Making check in PPS make[1]: Entering directory `/cygdrive/d/woody/svn/fox3/ZH-SG-PP/_test/PPS' make runtests.exe make[2]: Entering directory `/cygdrive/d/woody/svn/fox3/ZH-SG-PP/_test/PPS' g++ -g -O2 `cppunit-config --cflags` -g -O2 `cppunit-config --libs` -o runtests.exe runtests-TestMain.o runtests-RealTimeAccTest.o runtests-TestMain.o: In function `main': /cygdrive/d/woody/svn/fox3/ZH-SG-PP/_test/PPS/TestMain.cpp:10: undefined reference to `CppUnit::TextTestRunner::TextTestRunner(CppUnit::Outputter*)' /cygdrive/d/woody/svn/fox3/ZH-SG-PP/_test/PPS/TestMain.cpp:12: undefined reference to `CppUnit::TestFactoryRegistry::getRegistry(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /cygdrive/d/woody/svn/fox3/ZH-SG-PP/_test/PPS/TestMain.cpp:13: undefined reference to `CppUnit::TestRunner::addTest(CppUnit::Test*)' /cygdrive/d/woody/svn/fox3/ZH-SG-PP/_test/PPS/TestMain.cpp:14: undefined reference to `CppUnit::TextTestRunner::run(std::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, bool, bool)' /cygdrive/d/woody/svn/fox3/ZH-SG-PP/_test/PPS/TestMain.cpp:15: undefined reference to `CppUnit::TextTestRunner::~TextTestRunner()' /cygdrive/d/woody/svn/fox3/ZH-SG-PP/_test/PPS/TestMain.cpp:15: undefined reference to `CppUnit::TextTestRunner::~TextTestRunner()' runtests-RealTimeAccTest.o: In function `__tcf_0': /cygdrive/d/woody/svn/fox3/ZH-SG-PP/_test/PPS/RealTimeAccTest.h:10: undefined reference to `CppUnit::TestNamer::~TestNamer()' runtests-RealTimeAccTest.o: In function `AutoRegisterSuite': /usr/local/include/cppunit/extensions/AutoRegisterSuite.h:34: undefined reference to `CppUnit::TestFactoryRegistry::getRegistry(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /usr/local/include/cppunit/extensions/AutoRegisterSuite.h:36: undefined reference to `CppUnit::TestFactoryRegistry::registerFactory(CppUnit::TestFactory*)' runtests-RealTimeAccTest.o: In function `~AutoRegisterSuite': /usr/local/include/cppunit/extensions/AutoRegisterSuite.h:50: undefined reference to `CppUnit::TestFactoryRegistry::isValid()' /usr/local/include/cppunit/extensions/AutoRegisterSuite.h:51: undefined reference to `CppUnit::TestFactoryRegistry::unregisterFactory(CppUnit::TestFactory*)' runtests-RealTimeAccTest.o: In function `_ZN15RealTimeAccTest14getTestNamer__Ev': /cygdrive/d/woody/svn/fox3/ZH-SG-PP/_test/PPS/RealTimeAccTest.h:10: undefined reference to `CppUnit::TestNamer::TestNamer(std::type_info const&)' runtests-RealTimeAccTest.o: In function `~TestSuiteBuilderContext': /usr/local/include/cppunit/extensions/TestSuiteBuilderContext.h:101: undefined reference to `CppUnit::TestSuiteBuilderContextBase::~TestSuiteBuilderContextBase()' /usr/local/include/cppunit/extensions/TestSuiteBuilderContext.h:101: undefined reference to `CppUnit::TestSuiteBuilderContextBase::~TestSuiteBuilderContextBase()' What's wrong with my installation? Does anyone have a clue? Thanks! - narke -- Life is the only flaw in an otherwise perfect nonexistence -- Schopenhauer narke public key at http://subkeys.pgp.net:11371 (nar...@gm...) |
From: CppUnit d. m. l. <cpp...@li...> - 2009-11-22 08:03:30
|
The migration is completed. The trunk sources can be retrieved using: svn co https://cppunit.svn.sourceforge.net/svnroot/cppunit/trunk/cppunitcppunit A tarball of the old CVS repository is available in the "SVN Migration Archive" folder in the download section. Baptiste. 2009/11/19 Baptiste Lepilleur <bap...@gm...> > Hi all, > I plan to migrate CppUnit source code repository from CVS to subversion > this week-end unless someone voices strongly against it. > > This will make it easier to access the source repository from behind > corporate firewall and makes it easier for repository mirror to keep in sync > with the trunk (most DVCS can easily mirror a subversion trunk). > > Migration is done using iso-latin-1 encoding (I've already prepared a > svndump and there seems to be a few characters in unknown encoding in > changelog...). > > Let's me now if you see any issues with this. The old CVS repository > tarball will be made available on the download page for archival purpose. > > Baptiste. > |
From: CppUnit d. m. l. <cpp...@li...> - 2009-11-21 18:39:11
|
I believe this issue has been fixed in the trunk by andydent. See notes: http://cppunit.svn.sourceforge.net/viewvc/cppunit/trunk/cppunit/INSTALL-VS.Net2008.txt?view=markup 2009/11/17 CppUnit development mailing list < cpp...@li...> > Hi, I've spent a number of hours yesterday and today trying to get cppunit > up and going with VS 2008 (pro edition). > I can't find a getting started/trouble shooting guide anywhere. I get the > following message when I try to build TestRunner: > > 1>------ Build started: Project: TestRunner, Configuration: Debug Unicode > Win32 ------ > 1>Compiling... > 1>MsDevCallerListCtrl.cpp > 1>.\MsDevCallerListCtrl.cpp(67) : error C3505: cannot load type library > '{80CC9F66-E7D8-4DDD-85B6-D9E6CD0E93E2}' > 1>.\MsDevCallerListCtrl.cpp(67) : fatal error C1104: fatal error importing > libid: '80cc9f66-e7d8-4ddd-85b6-d9e6cd0e93e2' > 1>Creating browse information file... > 1>Microsoft Browse Information Maintenance Utility Version 9.00.30729 > 1>Copyright (C) Microsoft Corporation. All rights reserved. > 1>BSCMAKE: error BK1506 : cannot open file > '.\DebugUnicode\MsDevCallerListCtrl.sbr': No such file or directory > 1>Build log was saved at > "file://c:\cppunit-1.12.1\src\msvc6\testrunner\DebugUnicode\BuildLog.htm" > 1>TestRunner - 3 error(s), 0 warning(s) > ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== > > Any suggestions? > Thanks > Roger > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Cppunit-devel mailing list > Cpp...@li... > https://lists.sourceforge.net/lists/listinfo/cppunit-devel > |
From: CppUnit d. m. l. <cpp...@li...> - 2009-11-19 08:43:16
|
Hi all, I plan to migrate CppUnit source code repository from CVS to subversion this week-end unless someone voices strongly against it. This will make it easier to access the source repository from behind corporate firewall and makes it easier for repository mirror to keep in sync with the trunk (most DVCS can easily mirror a subversion trunk). Migration is done using iso-latin-1 encoding (I've already prepared a svndump and there seems to be a few characters in unknown encoding in changelog...). Let's me now if you see any issues with this. The old CVS repository tarball will be made available on the download page for archival purpose. Baptiste. |
From: CppUnit d. m. l. <cpp...@li...> - 2009-11-17 19:37:16
|
Hi, I've spent a number of hours yesterday and today trying to get cppunit up and going with VS 2008 (pro edition). I can't find a getting started/trouble shooting guide anywhere. I get the following message when I try to build TestRunner: 1>------ Build started: Project: TestRunner, Configuration: Debug Unicode Win32 ------ 1>Compiling... 1>MsDevCallerListCtrl.cpp 1>.\MsDevCallerListCtrl.cpp(67) : error C3505: cannot load type library '{80CC9F66-E7D8-4DDD-85B6-D9E6CD0E93E2}' 1>.\MsDevCallerListCtrl.cpp(67) : fatal error C1104: fatal error importing libid: '80cc9f66-e7d8-4ddd-85b6-d9e6cd0e93e2' 1>Creating browse information file... 1>Microsoft Browse Information Maintenance Utility Version 9.00.30729 1>Copyright (C) Microsoft Corporation. All rights reserved. 1>BSCMAKE: error BK1506 : cannot open file '.\DebugUnicode\MsDevCallerListCtrl.sbr': No such file or directory 1>Build log was saved at "file://c:\cppunit-1.12.1\src\msvc6\testrunner\DebugUnicode\BuildLog.htm" 1>TestRunner - 3 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== Any suggestions? Thanks Roger |
From: CppUnit d. m. l. <cpp...@li...> - 2009-11-12 09:48:18
|
Hi, I am a new user for Cppunit and haven't worked much on the .NET framework also. I have downloaded the current version of Cppunit i.e 1.12.1. I have Visual studio 2008 installed. The problem is that when building the cppunit project it does not extract a particular dll called testrunnerd.dll. Due to this I cannot run any test case. Any suggestions as to what might be the problem. Waiting for your input |
From: CppUnit d. m. l. <cpp...@li...> - 2009-11-12 09:45:05
|
---------- Forwarded message ---------- From: Tapan Singh <tap...@gm...> Date: Thu, Nov 12, 2009 at 3:13 PM Subject: Having problem while building the cppunit To: cpp...@li... Hi, I am a new user for Cppunit and haven't worked much on the .NET framework also. I have downloaded the current version of Cppunit i.e 1.12.1. I have Visual studio 2008 installed. The problem is that when building the cppunit project it does not extract a particular dll called testrunnerd.dll. Due to this I cannot run any test case. Any suggestions as to what might be the problem. Waiting for your input Tapan Singh |
From: CppUnit d. m. l. <cpp...@li...> - 2009-03-10 09:37:12
|
Hi all, I subscribed to the list last week and since it has been quite quiet I thought I could introduce myself as a heavy user of CppUnit that would like to contribute to its development. So if you think you could get some use of some extra hand, just drop me a hint. I do g++ on linux here. Cheers, JC! |
From: CppUnit d. m. l. <cpp...@li...> - 2008-02-20 22:27:23
|
> > > So the question to you is: what next? Does this seem like a worthwhile > > patch submission for cppunit? If so, should I post the patch to this > list? > > Or send it to someone particular? Is a patch against 1.12.0 good > enough, > > or should I generate a patch against the latest CVS sources? I've never > > tried to feed stuff back to a sourceforge project before, so I'm not > quite > > sure how to proceed. > > This sounds like a worthwhile patch. To increase your chances of > having it applied: make it easy on us developers by creating a patch > against CVS HEAD. > > The preferred method to submit a patch is the patch tracker page > at http://sourceforge.net/tracker/?group_id=11795&atid=311795 Okay -- I just submitted the patch against CVS HEAD to the patch tracker. It seems that 1.12.1 fixed a number of the issues that I had in 1.12.0, making the patch somewhat less interesting but hopefully still worthwhile. Please let me know if you have any problems with the patch. Dan |
From: CppUnit d. m. l. <cpp...@li...> - 2008-02-20 06:17:40
|
On Wed, Feb 13, 2008 at 02:03:52PM +0530, CppUnit development mailing list wrote: > Hi, > > Can anybody tell me when is the CppUnit 2.0 is getting released? Is > there any Beta version available? I just released the latest version: 1.12.1. It's got a few fixes over 1.12.0: New in CppUnit 1.12.1: ---------------------- * Assertion: - CPPUNIT_ASSERT_DOUBLES_EQUAL() now properly handles non-finite values, specifically NaN, +Inf, and -Inf. * Portability: - Fixed some compilation issue for QtTestRunner. - Code should build on Windows in UNICODE mode. Enjoy, -Steve |
From: CppUnit d. m. l. <cpp...@li...> - 2008-02-20 04:59:33
|
On Tue, Feb 12, 2008 at 04:16:02PM -0500, CppUnit development mailing list wrote: > I've produced a patch which quiets compiler warnings for > cppunit-1.12.0under g++- > 4.1. Is there some way I can contribute this patch to the project? Of course there is! > So the question to you is: what next? Does this seem like a worthwhile > patch submission for cppunit? If so, should I post the patch to this list? > Or send it to someone particular? Is a patch against 1.12.0 good enough, > or should I generate a patch against the latest CVS sources? I've never > tried to feed stuff back to a sourceforge project before, so I'm not quite > sure how to proceed. This sounds like a worthwhile patch. To increase your chances of having it applied: make it easy on us developers by creating a patch against CVS HEAD. The preferred method to submit a patch is the patch tracker page at http://sourceforge.net/tracker/?group_id=11795&atid=311795 Thanks, -Steve |
From: CppUnit d. m. l. <cpp...@li...> - 2008-02-13 08:34:07
|
Hi, Can anybody tell me when is the CppUnit 2.0 is getting released? Is there any Beta version available? Regards Anoop http://www.patni.com World-Wide Partnerships. World-Class Solutions. _____________________________________________________________________ This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at net...@pa... and delete this mail. _____________________________________________________________________ |
From: CppUnit d. m. l. <cpp...@li...> - 2008-02-12 21:50:30
|
Hi! I think this is a worthwile patch to be included in cppunit. For instance, I'm also working in a project where we want to avoid warnings from GCC following the guidelines of Scott Meyer's "Effective C++". Am Dienstag, 12. Februar 2008 schrieb CppUnit development mailing list: > I've produced a patch which quiets compiler warnings for > cppunit-1.12.0under g++- > 4.1. Is there some way I can contribute this patch to the project? [...] > --------------------------------------------------------------------------- > include/cppunit/extensions/TestFixtureFactory.h:16: warning: 'class > CppUnit::TestFixtureFactory' has virtual functions but non-virtual > destructor > > include/cppunit/extensions/TestFixtureFactory.h:29: warning: 'class > CppUnit::ConcretTestFixtureFactory' has virtual functions but non-virtual > destructor > --------------------------------------------------------------------------- [...] > So the question to you is: what next? Does this seem like a worthwhile > patch submission for cppunit? If so, should I post the patch to this list? -- Marcel Winandy |
From: CppUnit d. m. l. <cpp...@li...> - 2008-02-12 21:16:19
|
Hi - I've produced a patch which quiets compiler warnings for cppunit-1.12.0under g++- 4.1. Is there some way I can contribute this patch to the project? In more detail: I work in an environment where we do not allow compiler warnings about our code to persist. In detail, we run g++ (4.1 in my case) with "-ansi -W -Wall -Werror" and fail the build on any warning. All this would be fine, except that we get compiler warnings from the cppunit headers themselves: --------------------------------------------------------------------------- include/cppunit/extensions/TestFixtureFactory.h:16: warning: 'class CppUnit::TestFixtureFactory' has virtual functions but non-virtual destructor include/cppunit/extensions/TestFixtureFactory.h:29: warning: 'class CppUnit::ConcretTestFixtureFactory' has virtual functions but non-virtual destructor ---------------------------------------------------------------------------- For our own local purposes, I decided to patch 1.12.0 such that it would build under our no-warnings setting without problems. The patch is relatively small - covering 15 files and very few lines of code. I'm currently maintaining the patch locally, but I think it would make more sense to feed it back to the cppunit project since I think that it's broadly useful to have the unit-test framework be sufficiently clean to allow high levels of compiler-based checking without problems. (I know I'm not the only person with this issue -- see, for instance, http://www.calitko.org/source-talk/682.) So the question to you is: what next? Does this seem like a worthwhile patch submission for cppunit? If so, should I post the patch to this list? Or send it to someone particular? Is a patch against 1.12.0 good enough, or should I generate a patch against the latest CVS sources? I've never tried to feed stuff back to a sourceforge project before, so I'm not quite sure how to proceed. Thanks! Dan |
From: CppUnit d. m. l. <cpp...@li...> - 2008-02-01 05:29:48
|
Hi all, especially blep: Do you suppose we should make a new release? The current release, 1.12.0 doesn't build with gcc 4.3. CVS, however, does build. I'm happy to re-run the autotools and create the .tar.gz file. Should it be 1.14? Thanks, -Steve |
From: CppUnit d. m. l. <cpp...@li...> - 2007-10-18 11:35:26
|
Hi, Just downloaded: cppunit-1.12.0 I trying to get integration into Visual studio running I do follow INSTALL-WIN32.txt Quick Steps to compile & run a sample using the GUI TestRunner: - Open examples/examples.dsw in VC++ (contains all the samples). VC7 will ask you if you want to convert, anwser 'yes to all'. - Make HostApp the Active project - Compile Unfortunately this are the errors I got. 1>.\MsDevCallerListCtrl.cpp(67) : error C3505: cannot load type library '{80CC9F66-E7D8-4DDD-85B6-D9E6CD0E93E2}' 1>.\MsDevCallerListCtrl.cpp(67) : fatal error C1104: fatal error importing libid: '80cc9f66-e7d8-4ddd-85b6-d9e6cd0e93e2' 1>Creating browse information file... 1>Microsoft Browse Information Maintenance Utility Version 8.00.50727 1>Copyright (C) Microsoft Corporation. All rights reserved. 1>BSCMAKE: error BK1506 : cannot open file '.\debugunicode\MsDevCallerListCtrl.sbr': No such file or directory 1>Build log was saved at "file://e:\work\cppunit\cppunit-1.12.0\src\msvc6\testrunner\DebugUnicode\BuildLog.htm" 1>TestRunner - 3 error(s), 0 warning(s) -- W. Eryk Wolski |
From: CppUnit d. m. l. <cpp...@li...> - 2007-09-25 01:49:28
|
a simple cppunit code worked fine in Linux but failed in Cygwin. the libcppunit.a in cygwin was compiled from 1.12.0. the second statement in the below statement sequence lead to a core dump. however, if when i removed all test cases, below statements run okay. CppUnit::TestFactory ®istry = CppUnit::TestFactoryRegistry::getRegistry() runner.addTest( registry.makeTest() ); any clue? thanks. -- woody then sun rose thinly from the sea and the old man could see the other boats, low on the water and well in toward the shore, spread out across the current. |
From: CppUnit d. m. l. <cpp...@li...> - 2007-09-11 17:52:44
|
1) Do you have any static analysis capablility? (This is basically a code checker/parser that checks for a set of C++ coding standard violations) 2) Do you have any assembly branch coverage support? (This would check that all branches in the code are tested down to the assembly language code. Interested in PPC7410 assembly) 3) Are there any automated tools that parse C++ source and automatically generate a majority branch coverage? 4) Are there any training classes available? Thanks, Brian Brody NGC Software |
From: CppUnit d. m. l. <cpp...@li...> - 2007-08-14 17:33:34
|
I finally managed to find how to tackle the todo on assertion: - preserve the current scheme to implement an assertion: delegating to a = function to allow overloading and optional parameters - but make it so that the user condition is evaluated first (and not = SourceLocation check point object...) to make debugging easier. There is no change on existing assertion macros. But if you have written = some custom assertions, you will need to update the code. See = CPPUT_BEGIN_ASSERTION_MACRO() documentation in testinfo.h for an example = on how to update your existing assertion code. Let's me know if you run into any issues as I was not able to compile = this on all the usual compilers (only tested msvc71 & msvc80). Baptiste. |
From: CppUnit d. m. l. <cpp...@li...> - 2007-07-18 08:16:59
|
Hi, Viewtier has just finished integrating Parabuild and CppUnit. This includes CppUnit statistics and formatted logs. We would like to invite CppUnit community to join the beta program for Parabuild 3.2 to help us to test the integration. Please visit Viewtier website for details: http://www.viewtier.com/products/parabuild/eap/cppunit_eap.htm Thanks! Alex Pimenov api...@vi... www.viewtier.com |
From: CppUnit d. m. l. <cpp...@li...> - 2007-07-17 19:36:15
|
Hello, I am wondering if it is OK to post here a brief invitation to a beta program to test Parabuild integration with CppUnit. Thanks. Alex Pimenov api...@vi... www.viewtier.com |