From: Robert Goldman <rpgoldman@sift.info>
To: Avdi Grimm <avdi@avdi.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Regression testing for org-mode
Date: Thu, 23 Oct 2008 21:41:21 -0500 [thread overview]
Message-ID: <490135D1.4030208@sift.info> (raw)
In-Reply-To: <ecbcf0fb0810231703h5ff1f8e9s2628c6eb8f5ada5b@mail.gmail.com>
Avdi Grimm wrote:
> On Thu, Oct 23, 2008 at 7:57 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
>> I'm pessimistic that the colossal amount of work involved in wrapping
>> all of org-modes extensive and varied functionality into a test
>> framework can/should actually be completed. Would it be sufficient to
>> simply begin dealing with bug reports in a test-first manner?
>
> Absolutely. I do NOT recommend making an effort to get test coverage
> over existing code just for the sake of coverage - in my experience
> this usually leads a lot of work for brittle and not terribly useful
> tests. Put tests only around the areas you are about to change. Over
> time the coverage will grow.
>
>> Also, should we start tracking bug reports somewhere (worg), so that
>> they can be claimed, tested against, and repaired?
>
> Not a bad idea. Normally I'd recommend just going with an established
> bug tracker like Trac or Lighthouse, but since Org is so great for
> managing tasks it seems only right that the developers should "eat
> their own dogfood" by using Org to track tickets :-)
>
Actually, I'm not sure I necessarily agree with the notion of using Org
to track tickets. The reason is not that org mightn't be up to the job,
but that the use of org with git won't be up to it. systems like trac
and bugzilla are set up to allow outsiders to post bugs, but if we use
git, then we're really raising the bar for bug submission. Instead of
filling out a form, a bug reporter would now have to figure out how to
use git, pull the org file, modify it, and then either push it (which
would require someone to authorize him or her) or submit it to someone
else who would push it. That seems inappropriate to me --- when you're
developing software a good bug report is very valuable, and one
shouldn't turn them away.
Unless someone can figure out an easier way for people to submit bugs
with what worg has now, I'm inclined to say that trac or bugzilla would
be better.
Best,
r
next prev parent reply other threads:[~2008-10-24 2:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 16:03 Regression testing for org-mode Robert Goldman
2008-10-23 23:57 ` Eric Schulte
2008-10-24 0:03 ` Avdi Grimm
2008-10-24 2:41 ` Robert Goldman [this message]
2008-10-24 3:04 ` worg for bug reports and feature requests was: (Regression testing for org-mode) Eric Schulte
2008-10-24 4:42 ` Robert Goldman
2008-10-24 14:12 ` Sebastian Rose
2008-10-24 14:27 ` Avdi Grimm
2008-10-24 20:44 ` Eric Schulte
2008-10-24 23:54 ` Eric Schulte
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=490135D1.4030208@sift.info \
--to=rpgoldman@sift.info \
--cc=avdi@avdi.org \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).