From: Rainer M Krug <r.m.krug@gmail.com>
To: Christian Egli <christian.egli@sbs.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Test framework needed
Date: Wed, 30 Mar 2011 16:30:54 +0200 [thread overview]
Message-ID: <4D933E9E.7030907@gmail.com> (raw)
In-Reply-To: <87vcz03d4p.fsf@sbs.ch>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30/03/11 16:18, Christian Egli wrote:
> Rainer M Krug <r.m.krug@gmail.com> writes:
>
>>> 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)?
>
> Before you go too far with this; Orgmode already contains a unit test
> suite. Look at the README in the testing directory
> (http://orgmode.org/w/?p=org-mode.git;a=blob_plain;f=testing/README.org;hb=HEAD)
>
But it does not look as if it is used very often... There are not many
test org files, and I did not se anything which compares the resulting
exported / tangle file with an expected output?
Please correct me if I am missing something.
This suite should actually be updated with effectively each patch which
introduces new features and run after each patch.
So is it only necessary to add meat to this framework?
Rainer
- --
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/
iEYEARECAAYFAk2TPp4ACgkQoYgNqgF2egpBZQCfQN+g3J2+BiyKaWzh6o847mZS
PR4An0aW0Di6vfgzwsJgwfK4FajL65WP
=9/CW
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-30 14:31 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
2011-03-30 14:26 ` MidLifeXis at PerlMonks
2011-03-30 14:18 ` Christian Egli
2011-03-30 14:30 ` Rainer M Krug [this message]
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=4D933E9E.7030907@gmail.com \
--to=r.m.krug@gmail.com \
--cc=christian.egli@sbs.ch \
--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).