RE: common C++ test suite

[Chad Yates]

Attached is a zip file containing the msvc++ 6.0 project file.  I made no
effort to setup the release target environment, just the debug one.

It resides in commoncpp2/win32/tests is called ccxx_testsuite and builds
it's debug output in commoncpp2/win32/Debug like the other tests.  it
expects to find it's source files in commoncpp2/tests, and may reference at
least 1 file that I have not submitted yet (SampleNode.cpp/SampleNode.cpp).

The file b64test.cpp I think I included in the source code zip can safely be
omitted since it was a isolated set of test cases for the b64 bugs I
previously submitted, and they are included in test_urlstring.cpp.

Please let me know if you have any trouble. :)

,Chad

P.S. You'll probably want to add it to some of the ccxx workspaces so it
gets exposure.

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden Behalf Of
> Federico Montesino Pouzols
> Sent: Thursday, January 30, 2003 2:49 AM
> To: Chad Yates
> Cc: address@hidden; bug-commoncpp
> Subject: Re: common C++ test suite
>
>
>
>       Hi,...
>
> On Wed, Jan 29, 2003 at 10:41:34PM -0800, Chad Yates wrote:
> > Common C++ community,
> >
> > As some of you may remember, I wrote some test suites in
> cppunit last month
> > and I would like to submit them as the beginnings of a common
> C++ test suite
> > as we had discussed then.  however it has a couple of issues I
> am hoping a
> > more experienced common c++ developer or maintainer can help
> with, as I am a
> > gnu autoconfig/automake newbie, I'll admit it. :)  also since I
> typically
> > develop using m$ visual studio 6.0 I'm not that proficient with
> > developing/debugging on the linux environment.
> >
> > My date classes have some tests that are failing now with the
> recent patches
> > submitted that add the new YYYY/MM/DD style formats instead of
> the YYYYMMDD
> > formats.  whether the interface is changing or whether the
> tests need to be
> > updated to the new format needs to be determined.
> >
>
>       I would expect Marcelo's opinion, though I think that we
> should keep backwards compatibility.
>
> > My persistence tests (pretty extensive), work fine under
> windows, but throw
> > exceptions under linux.  I don't yet know why, and since I
> haven't come to
> > grips with a linux debugger yet (I've been babied by VC++'s gui
> debugger), I
> > can't dig into the reason yet.  I have another test case under
> windows, but
> > am not going to add it at this time as it has some linux
> compilation issues.
> >
> > There are generalized test classes for the digest tests, however I could
> > never seem to get decent results out of the SHA digests on
> windows, they may
> > work fine under linux, though the testcase registration macros
> are commented
> > out right now.
> >
> > There are also tests for the urlstring file including base64
> encode decode.
> >
> > I have attached a zip file containing a zipped directory called
> ccxx_tests
> > designed to be uncompressed under the commoncpp2 main
> directory.  eventually
> > I would hope the contents would live in tests instead, and all
> the existing
> > tests changed to components of the cppunit test suites, or something
> > similar.
> >
>
>       Um, I would like the new tests to go directly into tests/, and
> integrate the old tests as soon as possible. Since there seems to be a
> few issues to solve, I would put the new tests there now for the
> development branch, and, when these issues are clarified, commit the
> new test suite for the stable releases. This would be a very
> interesting new feature for 1.0.9. It would also be interesting to
> include the VC++ project files for the test suite.
>
>       Do you agree with this plan?
>
> > I have also attached a diff of the changes I made to the
> configure.in and
> > Makefile.am to get it to build for me on my linux machine,
> however, I didn't
> > get the check for cppunit to work to my liking, and am sure the
> changes I
> > made were not ideal.  hopefully someone with more expertise in
> > autoconf/automake can make better changes there.
> >
> > Anyway, I wanted to get this out there and in cvs so others can
> contribute
> > if wanted, and so we would have somewhat of a base to start/learn from.
> > Also, it would be a good habit for contributors to get the hang
> of adding
> > suites/testcases while finding/resolving bugs and making
> enhancements. This
> > way some inadvertant sideffects can hopefully be avoided.
> >
>
>       I totally agree.
>
> > Cheers,
> >
> > chad
> >
> > P.S. I spoke with albert today, and he will be contributing his
> testcases
> > etc a bit later.  Feel free to contact me if you have questions,
> > comments/suggestions, or if you have trouble compiling it.  I will
> > contribute new suites/testcases as I develop them.
>
>
>
> > _______________________________________________
> > Bug-commoncpp mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp

ccxx_tests_msvc_project.zip
Description: Zip compressed data