unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Barry OReilly <gundaetiapo@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Dmitry Gutov <dgutov@yandex.ru>, emacs-devel@gnu.org
Subject: Re: Simple lisp-tests.el and commit privs
Date: Wed, 21 Aug 2013 19:06:42 -0400	[thread overview]
Message-ID: <CAFM41H0_smgFQ1i4jwNffHn2_qELRy=Gqcn3oF8DrnxBBrR32w@mail.gmail.com> (raw)
In-Reply-To: <jwvfvu49jgn.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

> You may have to run the test by first flushing all the code to the
> left margin before reindenting

That would certainly make the tests better. Only testing preindented
buffers is good but insufficient. What you describe is a good way to
test non preindented buffers.

> Oh, you're referring to known indentation problems, where you want to
> have the test but have it be marked as "expected".
>
> Yes, that's currently not really supported: I try to put "FIXME" on
> the corresponding lines, but very often an incorrect indentation on
> one line impact subsequent lines as well, so not only does the
> "diff" not care about those FIXME markers, but you can get false
> positives or false negatives to boot.

Sounds more complex than using ERT :expected-result.

If I indicate :expected-result is :failed on an invocation of a
test/indent test from ERT, it would suppress all the expected
successes because of one expected failure. Alternatively, the test
could filter out lines with "FIXME", but that's ugly.

I think finer grained ERT tests that can be marked as :expected-result
of :passed or :failed (and don't need to parse for FIXMEs) are the
better approach for test/automated 'make check' tests.

[-- Attachment #2: Type: text/html, Size: 1416 bytes --]

      reply	other threads:[~2013-08-21 23:06 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
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 [this message]

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFM41H0_smgFQ1i4jwNffHn2_qELRy=Gqcn3oF8DrnxBBrR32w@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).