From: Aankhen <aankhen@gmail.com>
To: Manuel Giraud <manuel.giraud@univ-nantes.fr>,
Rainer M Krug <r.m.krug@gmail.com>,
emacs-orgmode@gnu.org, Christian Egli <christian.egli@sbs.ch>
Subject: Re: Re: Test framework needed
Date: Thu, 31 Mar 2011 01:44:55 +0530 [thread overview]
Message-ID: <AANLkTimFfN7KSvp+8cZ_n=co9x3LE67SBCOJnGjQ1eEG@mail.gmail.com> (raw)
In-Reply-To: <87r59o8wum.fsf@univ-nantes.fr>
On Wed, Mar 30, 2011 at 20:43, Manuel Giraud
<manuel.giraud@univ-nantes.fr> wrote:
> Rainer M Krug <r.m.krug@gmail.com> writes:
> [snip]
>
>> 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.
>
> Which renders this framework far less automatic. I think that having a
> set of org files against which one could try any export and *see* that
> the results are almost correct would be enough.
I think the “automated” part refers to running the tests. What you
suggest—having a set of files that you could manually export to verify
the results—wouldn’t be of much help, IMHO. First, it’d require a lot
more time than executing a single command and checking the summary at
the end. Second, it’d be very error-prone.
A comprehensive automated test suite gives people writing patches an
easier way to perform regression testing and catch any unintended
consequences. On the other hand, it /does/ take a lot of effort to
keep it in sync with the codebase… maybe we need a Test Fairy. ;-)
Aankhen
next prev parent reply other threads:[~2011-03-30 20:15 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
2011-03-30 15:13 ` Manuel Giraud
2011-03-30 20:14 ` Aankhen [this message]
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='AANLkTimFfN7KSvp+8cZ_n=co9x3LE67SBCOJnGjQ1eEG@mail.gmail.com' \
--to=aankhen@gmail.com \
--cc=christian.egli@sbs.ch \
--cc=emacs-orgmode@gnu.org \
--cc=manuel.giraud@univ-nantes.fr \
--cc=r.m.krug@gmail.com \
/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).