emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <r.m.krug@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Test framework needed
Date: Wed, 30 Mar 2011 16:22:16 +0200	[thread overview]
Message-ID: <4D933C98.3090207@gmail.com> (raw)
In-Reply-To: <87hbakg0l0.fsf@ericabrahamsen.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 30/03/11 16:11, Eric Abrahamsen wrote:
> On Wed, Mar 30 2011, Rainer M Krug wrote:
> 
>> On 30/03/11 15:46, Eric Abrahamsen wrote:
>>> On Wed, Mar 30 2011, Rainer M Krug wrote:
>>>
>>>> Hi
>>>>
>>>> I was bitten again from an unintended regression in org-mode, and that
>>>> the second time in two weeks.
>>>>
>>>> I am probably not the right person to suggest this, but I think it is
>>>> time to introduce a test framework for org-mode, to ensure that the
>>>> (without doubt useful) approach to develop org-mode does not lead to
>>>> regressions.
>>>
>>> This would be the page to start with, though the most likely candidate
>>> (Elisp Regression Testing) is only available in Emacs trunk at the
>>> moment…
>>>
>>> http://www.emacswiki.org/emacs/UnitTesting
>>
>> Am I right in assuming, that all of the possible test frameworks would
>> require org files and the expected output (tengle, export to ...,
>> agenda, ...)? In this case, would it make sense to start collecting
>> those, as they can easily be user contributed, consequently representing
>> a cross section of the use cases (even not intended use cases)?
> 
> Yup, what you would need is some org source files that exercise all of
> the possible export options (for testing export, for example), including
> weird edge cases, and then ERT (if that's what we ended up using) would
> provide handy functions for making sure the export output matches
> expectations. The excellent gentleman who created the ODT exporter,
> whose name currently escapes me, has already created test files for his
> exporter—that would be a perfect place to start.
> 
> Covering all of org's various functions would end up being a bit of a
> PITA, though you're quite right that it's an excellent idea, and will
> become more and more necessary.

So would there be a possibility of "normal org users" (if there is such
a thing ...) to contribute to this?

What would be needed? Any specific structure of the org files?

Rainer

> 
> E
> 
> 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Tel:        +33 - (0)9 53 10 27 44
Cell:       +27 - (0)8 39 47 90 42
Fax (SA):   +27 - (0)8 65 16 27 82
Fax (D) :   +49 - (0)3 21 21 25 22 44
Fax (FR):   +33 - (0)9 58 10 27 44
email:      Rainer@krugs.de

Skype:      RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2TPJgACgkQoYgNqgF2egoWKwCeMjWgggD7JMhVTrQTHe3f7n6s
VhgAn2CG25hOa1Q4RPufarreQVYlezHm
=18s2
-----END PGP SIGNATURE-----

  reply	other threads:[~2011-03-30 14:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 13:01 Test framework needed Rainer M Krug
2011-03-30 13:46 ` Eric Abrahamsen
2011-03-30 13:56   ` Rainer M Krug
2011-03-30 14:11     ` Eric Abrahamsen
2011-03-30 14:22       ` Rainer M Krug [this message]
2011-03-30 14:26       ` MidLifeXis at PerlMonks
2011-03-30 14:18     ` Christian Egli
2011-03-30 14:30       ` Rainer M Krug
2011-03-30 15:13         ` Manuel Giraud
2011-03-30 20:14           ` Aankhen
2011-03-30 21:39             ` Eric Schulte
2011-03-30 21:42         ` Eric Schulte
2011-03-31  0:19           ` Suvayu Ali
2011-03-31  3:40             ` Eric Schulte
2011-03-31  7:15               ` Rainer M Krug

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=4D933C98.3090207@gmail.com \
    --to=r.m.krug@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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).