emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Robert Goldman <rpgoldman@sift.info>
Cc: emacs-orgmode@gnu.org
Subject: Re: Regression testing for org-mode
Date: Thu, 23 Oct 2008 16:57:22 -0700	[thread overview]
Message-ID: <87wsfyx3tp.fsf@gmail.com> (raw)
In-Reply-To: <4900A06B.8020605@sift.info> (Robert Goldman's message of "Thu, 23 Oct 2008 11:03:55 -0500")


I've added a "testing tools" section and a simple example of an org-mode
test using ert to Sebastian's org testing page in worg.  I don't mean to
advocate for ert, it is simply the only elisp testing framework that I
have any experience with.

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?

Also, should we start tracking bug reports somewhere (worg), so that
they can be claimed, tested against, and repaired?

Thanks -- Eric

Robert Goldman <rpgoldman@sift.info> writes:

> There's a page on the EmacsWiki describing schemes for unit/regression
> testing in emacs lisp:
>
> http://www.emacswiki.org/cgi-bin/wiki/UnitTesting
>
> Perhaps we could pick up one of these?  I haven't evaluated any of them.
>
> In response to Ben Alexander's question, yes, sometimes the screen
> output is what you care about, but a big advantage of emacs is that the
> screen output is a big array of text, so we could check it (it's a lot
> worse, if it's just a bit map...).  Sure, we can't always do that, but I
> think in many cases we could just grab up a buffer's contents and
> compare it against a "right answer."
>
> best,
> r
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2008-10-23 23:56 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 [this message]
2008-10-24  0:03   ` Avdi Grimm
2008-10-24  2:41     ` Robert Goldman
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=87wsfyx3tp.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rpgoldman@sift.info \
    /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).