emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Tom Breton (Tehom)" <tehom@panix.com>
To: Martin Pohlack <mp26@os.inf.tu-dresden.de>
Cc: emacs-orgmode@gnu.org, Tom Breton <tehom@panix.com>
Subject: Re: Proposal: Emtest as tester
Date: Thu, 27 May 2010 16:13:28 -0400	[thread overview]
Message-ID: <df3d8404889743e37c6ceb1c6e836883.squirrel@mail.panix.com> (raw)
In-Reply-To: <4BFB8DB3.5050807@os.inf.tu-dresden.de>

> Hi Tom,
>
>>
> [...]
>
> I made an attempt earlier to propose a testing framework and wrote some
> thoughts in an email thread:
>
> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg22558.html

I read that.  Interesting.

> Would your proposal cover my example-based approach?  How hard would it
> be to turn a typical bug report into a test case?

Not hard at all.  Most of what you propose is already supported.  You
would put both the input and expected output in FOO/examples/UNIQUE-NAMES

The sequence of commands can easily be made into a test case. 
`emt:insert' inserts the template for you (choose `emt:insert-test'), then
paste it in.

Rather than saving the buffer, you probably want to do it all inside a
mock buffer, like (excuse the online-editor formatting)

(emtb:with-buf (:file INPUT-FILE-NAME)
(operations)
(emtb:buf-contents-matches (:file OUTPUT-FILE-NAME))

For testing only visible output, you'd presumably use org-export-visible
and compare that buffer's contents to what's expected.

Wildcard comparisons in files are not yet supported.  I will take that as
a feature request.

Tom Breton (Tehom)

  reply	other threads:[~2010-05-27 20:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 22:24 org-html link building diff Tom Breton (Tehom)
2010-05-01 12:01 ` Carsten Dominik
2010-05-15 12:29 ` Carsten Dominik
2010-05-15 21:37   ` Tom Breton (Tehom)
2010-05-16  5:03     ` Carsten Dominik
2010-05-18  0:59       ` Tom Breton (Tehom)
2010-05-18  4:47         ` Carsten Dominik
2010-05-18 12:26           ` Sebastian Rose
2010-05-16  5:20     ` Carsten Dominik
2010-05-18  1:01       ` Test-file naming conventions - mine and suggested for org Tom Breton (Tehom)
2010-05-21 11:27         ` Carsten Dominik
2010-05-24 21:26           ` Proposal: Emtest as tester Tom Breton (Tehom)
2010-05-24 22:56             ` Dan Davison
2010-05-27 20:02               ` Tom Breton (Tehom)
2010-05-25  6:48             ` Carsten Dominik
2010-05-25  8:43             ` Martin Pohlack
2010-05-27 20:13               ` Tom Breton (Tehom) [this message]
2010-06-07 16:11                 ` Benjamin Andresen

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=df3d8404889743e37c6ceb1c6e836883.squirrel@mail.panix.com \
    --to=tehom@panix.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mp26@os.inf.tu-dresden.de \
    /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).