Re: [Cppunit-devel] 1.6.1 changes

[Baptiste L. <bl...@cl...>]

----- Original Message -----
From: "Steve M. Robbins" <ste...@vi...>
To: "Cpp Unit Develpment Mailing List" <cpp...@li...>
Sent: Saturday, September 29, 2001 8:28 PM
Subject: [Cppunit-devel] 1.6.1 changes


> On Thu, Sep 27, 2001 at 02:59:04PM +0200, Baptiste Lepilleur wrote:
> > Quoting "Steve M. Robbins" <ste...@vi...>:
>
> > > Well, so far, we aren't exactly inundated with bug reports.  So making
> > > the change at the end of next week is probably fine.
> > >
> > > At any rate, ONCE the branch is made, the idea is to merge 1.6.x
> > > bugfix changes to the main trunk (if applicable) as you do them.
> > > Any delay of the merge just makes it more complicated.
> >
> >   Well, I was thinking about a slighlty tighter time schedule :-)
> >   - have the branch made this week-end, and
> >   - release 1.8.0 by the end of next week-end...
>
> Ah, I had originally misunderstood your timetable.
>
> OK, I have time this weekend to do 1.6.1, and then I'll make the branch
> at that point.  Deal?
    Sound good to me.

> So the question becomes: what can we reasonably include in 1.6.1?
> The changes I'd like to make are the following
>
> 1. Fix the doc file to include cookbook.html.
> 2. Eliminate the repeated includes pointed out by Bob S.
> 3. Include the (non-OSX) mac config.
> 4. Include an FAQ available both in the sources and via the web.
> 5. Updated docs, especially the intro/cookbook.

  I also comitted a little while ago the TestCallerTest fix (nothing major).

> I can certainly do #1 and #2 myself.  For #3 to make it in, someone
> (Duane?)  will have to supply the relevant preprocessor symbols to
> use.  Since Baptiste has already expressed interest in the FAQ, I'm
> happy to leave that to him should he wish it; otherwise I'll throw
 > something together at the last minute.

  Wouldn't mean to. Though how would you organize the FAQ ?

    I can think of 3 sections should come out:
- Windows specifics
    Well, we already have 3 questions compiled from FAQ on the forum. More
are welcome.

- Unix specifics (would this includes Mac OS X?)
    I'm the dumb boy there here. How to I build the examples, where do I
found the executable of the build samples...

- Generic
    Where is the XML output ? ;-)

> To aid the FAQ compiler, it would be helpful to send in candidate
> questions and answers.  Perhaps those of you who just joined us
> recall one or two large stumbling blocks?  Or those of you reading
> the user- and help- forums see questions coming up over and over?
>
> Similarly, corrections and additions to other bits of docs would be
> greatly appreciated!  In particular, the intro page (cppunit.sf.net)
> cookbook need work.  Learning to use CppUnit was quite troublesome in
> my experience, so this is one area that should get extra attention, I
> feel.
    I skimmed through the cookbook and I noticed that the macros are never
evoked. I think that the macros are actually the fastest way to get started
with CppUnit (especially on VC++ where you can have VC++ macro or add-ins
generating most of the code for you).

    That's how I'm introducing CppUnit at work. I present a Fixture, and
show how to add tests and what are the macro available to write assertions.
How a suite is created for the fixture and where you can find it in the
TestRunner. That way you can start using the framework without having to
understand it. Face it, most of the guys don't really care how CppUnit
works. They just want it to make their life easier.

    They might want to start understanding the whole thing when they want to
write attipical test (functionnal test), or reach the limit of CppUnit and
want to enhance it...

    Of course, I don't think that "for tomorow TODO".

    Oh, by the way, I have those nifty Workspace Whiz template that allow
the owner of that add-ins to create a new test case class and had it to the
project in a few mouse click. Where should I put it in the CppUnit dist ? I
was thinking of contrib/msvc/.

> Are there other items to include in 1.6.1 that can be done today or
> tomorrow (especially on the non-unix side)?

    Well, I actually got a bug report (somewhat MFC don't open the right
dialog when browsing the unit test). I'll try to reproduce it before
attempting solving it. Since it's MFC black magic and I'm not really an
expert in that area, I don't expect a quick resolution. I'll have to
reproduce the bug first.

>
> -Steve
>
> P.S.  Don't worry about the short deadlines.  We can make 1.6.2 at any
> time.
>
>
> >   By the way, has xprogramming.org been contacted, the page haven't been
> > updated ?
>
> Not by me.  I'm only handling the SF release process (and I'm going to
> do the next Debian release, too).  Baastien said he did a freshmeat
> announcement.  I don't know of any other channels.  I'd suggest: if
> you know of a community of potential interest then make the
> announcement and let us on cppunit-devel know.

    Ok. I'll contact Ron...

    Baptiste.
---
Baptiste Lepilleur <gai...@fr...>   http://gaiacrtn.free.fr/index.html
Author of The Text Reformatter, a tool for fanfiction readers and writers.
Language: English, French (Well, I'm French).