From: Barry OReilly <gundaetiapo@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Simple lisp-tests.el and commit privs
Date: Sun, 18 Aug 2013 18:05:26 -0400 [thread overview]
Message-ID: <CAFM41H2VMsPXg6aekL07CgxcfSu8Pbb1qEaFQKzqX8M64heHcQ@mail.gmail.com> (raw)
In-Reply-To: <87y584c6gv.fsf@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
Thanks for the link to the previous discussion, Dmitry.
Dmitry:
>> Don't you think it would be better to have these tests in
>> test/automated/ruby-mode-tests.el?
Stefan:
> I find it inconvenient, actually, because when the test fails, it's
> a handy to be able to have a ruby-mode buffer where I can try out
> sexp movement and indentation functions "in the usual way", together
> with Edebug if needed.
Surely there's a way to provide this debugging use case without
ostracizing the test from the automated test suite. Why not have a
ert-with-temp-buffer which if the test fails (within the form), a file
would be saved off with the buffer contents. Ideally the test case
name would be in the generated filename.
Stefan:
> use test/indent the general indentation rules, and use ERT rules to
> check how indentation obeys the various indentation variables
It looks like the test/indent tests are only good for null-diff
general indentation rules. And worst of all not automated.
[-- Attachment #2: Type: text/html, Size: 1148 bytes --]
next prev parent reply other threads:[~2013-08-18 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 4:12 Simple lisp-tests.el and commit privs Barry OReilly
2013-07-21 23:08 ` Xue Fuqiao
2013-07-25 19:09 ` Stefan Monnier
2013-08-14 17:49 ` Barry OReilly
2013-08-14 21:23 ` Dmitry Gutov
2013-08-18 22:05 ` Barry OReilly [this message]
2013-08-19 3:06 ` Stefan Monnier
2013-08-19 3:09 ` Stefan Monnier
2013-08-19 16:41 ` Barry OReilly
2013-08-20 5:23 ` Stefan Monnier
2013-08-20 16:04 ` Barry OReilly
2013-08-20 20:54 ` Stefan Monnier
2013-08-21 23:06 ` Barry OReilly
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFM41H2VMsPXg6aekL07CgxcfSu8Pbb1qEaFQKzqX8M64heHcQ@mail.gmail.com \
--to=gundaetiapo@gmail.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.