From: Dalibor Topic <robilad@yahoo.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Brian Jones <cbj@gnu.org>, Stephen Crawley <crawley@dstc.edu.au>,
John Leuner <jewel@pixie.co.za>, Alex Lau <alex@dentonlive.com>,
kissme-general@lists.sourceforge.net,
mauve-discuss@sources.redhat.com
Subject: Re: [Kissme-general] Re: Should I or not submit changes?
Date: Thu, 18 Jul 2002 08:06:00 -0000 [thread overview]
Message-ID: <20020718150633.26992.qmail@web10001.mail.yahoo.com> (raw)
In-Reply-To: <1026998457.6497.70.camel@elsschot>
Hi Mark,
--- Mark Wielaard <mark@klomp.org> wrote:
> On Wed, 2002-07-17 at 11:32, Dalibor Topic wrote:
> > The major point junit has for it, in my opinion,
> is
> > the amount of documentation surrounding it: books,
> > tutorials etc. It seems to be easy to find
> answers.
> > That could lower the entry barrier for fresh mauve
> > contributors.
>
> Having a simple/short but good documentation and
> template/example file
> for Mauve will probably be more important for people
> wanting to
> contribute then JUnit support though.
I fully agree. The lack of a simple, step-by-step
guide to adding new tests to mauve, is the major
stumbling block for beginners. It seems to pop up
about once every three months, and I've even asked for
it myself ;) Documenting good testing practices should
also help quite a bit.
best regards,
dalibor topic
__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com
next prev parent reply other threads:[~2002-07-18 15:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1026843874.3494.68.camel@bapli>
2002-07-16 17:48 ` Stephen Crawley
2002-07-16 20:05 ` Brian Jones
2002-07-17 2:32 ` Dalibor Topic
2002-07-18 6:21 ` Mark Wielaard
2002-07-18 8:06 ` Dalibor Topic [this message]
2002-07-19 3:51 ` Chris Gray
2002-07-18 6:35 ` Brian Jones
2002-07-17 7:13 ` Andrew Haley
2002-07-18 6:32 ` Mark Wielaard
2002-07-18 6:56 ` Andrew Haley
2002-07-18 7:07 ` Dalibor Topic
2002-07-17 8:33 ` Alex Lau
2002-07-17 8:49 ` Stephen Crawley
2002-07-17 12:15 ` Alex Lau
2002-07-17 9:02 ` Dalibor Topic
2002-07-18 6:26 ` John Leuner
2002-07-18 6:00 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020718150633.26992.qmail@web10001.mail.yahoo.com \
--to=robilad@yahoo.com \
--cc=alex@dentonlive.com \
--cc=cbj@gnu.org \
--cc=crawley@dstc.edu.au \
--cc=jewel@pixie.co.za \
--cc=kissme-general@lists.sourceforge.net \
--cc=mark@klomp.org \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).