From: Rainer M Krug <r.m.krug@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Test framework needed
Date: Wed, 30 Mar 2011 15:01:48 +0200 [thread overview]
Message-ID: <4D9329BC.6000106@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
org is, as I see it, complex and is getting broader and broader - time
management, task management, literate programming, recipes (I like the
idea), all have different (possibly contradicting?) requirements. And I
think it is getting more and more difficult for new contributors to have
the overview to make sure that something they are contributing actually
does not break something else.
As I think it would be *really bad* idea to split org, I think that it
needs to be assured that no regressions are introduced.
Unfortunately I have no idea about elisp and can therefore not
contribute to the framework itself, but I guess all of us could
contribute small org files as test cases and expected resulting outputs
(exports, tangling, agenda files, ...). If the framework could
accommodate those, everybody could help to bring together a (definitely
not perfect) test framework, that would bring org at least one step
closer to error-free growth.
I have to add I really love org and babel and have no idea what I would
use instead for literal programming in R.
Cheers,
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/
iEYEARECAAYFAk2TKbwACgkQoYgNqgF2egpQJwCdG7C+3Ft+xGyLBiwY6aBwMLaC
TIIAn0RD3ypbvkfE1RAL4FK3ZwmnERdE
=GlJt
-----END PGP SIGNATURE-----
next reply other threads:[~2011-03-30 13:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 13:01 Rainer M Krug [this message]
2011-03-30 13:46 ` Test framework needed 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
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=4D9329BC.6000106@gmail.com \
--to=r.m.krug@gmail.com \
--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).