unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: 22471@debbugs.gnu.org
Subject: bug#22471: ert batch should print compile parsable error messages
Date: Wed, 27 Jan 2016 09:15:44 +0000	[thread overview]
Message-ID: <87bn878jsv.fsf@russet.org.uk> (raw)


Currently, when running in batch, ert prints out messages like so:


Running 24 tests (2016-01-27 09:05:17+0000)
   passed   1/24  buffer-string=
   passed   2/24  buffer=
...
   passed  22/24  sisyphus-test-with-find-file
   passed  23/24  to-string
   passed  24/24  with-temp-buffers

Ran 24 tests, 23 results as expected, 1 unexpected (2016-01-27 09:05:18+0000)

1 unexpected results:
   FAILED  crash-out

It would be nice to add some compilation-mode parsable data to this. So,
something like


   passed   1/24  buffer-string=  (in ./test.sisyphus-test.el:22:)

It would also be nice to add colourisation: red and green for passed and
failed. In the idea world, these could be added as ansi colour codes to
the batch output of ERT. They should work on the command line then also.

More of an RFE than a bug, but it is odd that compilation mode works
with lots and lots of test frameworks, but not Emacs'

Phil





             reply	other threads:[~2016-01-27  9:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  9:15 Phillip Lord [this message]
2016-01-27 16:06 ` bug#22471: ert batch should print compile parsable error messages Eli Zaretskii
2016-01-27 21:53   ` Phillip Lord
2016-01-28  1:28     ` Glenn Morris
2016-01-28 17:14       ` Phillip Lord
2020-08-20 16:39 ` Lars Ingebrigtsen
2020-08-20 16:51   ` Philipp Stephani
2021-10-23  0:15   ` Stefan Kangas
2021-10-24 12:57     ` Lars Ingebrigtsen
2021-10-24 14:27       ` Stefan Kangas
2021-10-24 20:01         ` Lars Ingebrigtsen
2022-01-24 12:54           ` Lars Ingebrigtsen

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=87bn878jsv.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=22471@debbugs.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.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).