From: "Eric Schulte" <schulte.eric@gmail.com>
To: Aankhen <aankhen@gmail.com>
Cc: Christian Egli <christian.egli@sbs.ch>,
emacs-orgmode@gnu.org,
Manuel Giraud <manuel.giraud@univ-nantes.fr>,
Rainer M Krug <r.m.krug@gmail.com>
Subject: Re: Re: Test framework needed
Date: Wed, 30 Mar 2011 15:39:58 -0600 [thread overview]
Message-ID: <87oc4sp9hx.fsf@gmail.com> (raw)
In-Reply-To: AANLkTimFfN7KSvp+8cZ_n=co9x3LE67SBCOJnGjQ1eEG@mail.gmail.com
Aankhen <aankhen@gmail.com> writes:
> 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 an "automatic" solution would involve running a batch Emacs
process which loads up Org-mode and then loads and runs the existing
test suite. This would be both easily automatable and would allow
testing of various versions of Emacs with relative ease.
Best -- Eric
next prev parent reply other threads:[~2011-03-30 22:45 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
2011-03-30 21:39 ` Eric Schulte [this message]
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=87oc4sp9hx.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=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).