From: Frank Terbeck <ft@bewatermyfriend.org>
To: Marc Chantreux <eiro@phear.org>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: test anything? (Re: My Guile Hacker Handbook)
Date: Thu, 23 Jul 2020 10:12:32 +0200 [thread overview]
Message-ID: <87blk6vedr.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <20200723064626.GA7119@prometheus.u-strasbg.fr> (Marc Chantreux's message of "Thu, 23 Jul 2020 08:46:26 +0200")
Hi,
Marc Chantreux wrote:
[…]
>> Hope it can help someone to jump in and hack.
>
> i just discovered srfi 64 thanks to your page. the thing is: when it
> comes to test report, i have one simple rule: TAPs or GTFO.
>
> so i saw a TAP lib for guile (https://github.com/xevz/guile-tap) which
> is not mentioned in the testanything.org/ or guile documentation.
I'm similar with test-reporting. TAP is nice and available for every
language under the sun. So years back, because I couldn't find a frame-
work that would for Guile, I wrote ¹, which emits TAP as well. But it
does not replicate Perl's API. So no "ok" procedure and things like
that.
I don't think many people use it, but I thought I'd mention it anyway.
Regards, Frank
¹ https://github.com/ft/scm-test-tap
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2020-07-23 8:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 6:18 My Guile Hacker Handbook Jérémy Korwin-Zmijowski
2020-07-23 6:46 ` test anything? (Re: My Guile Hacker Handbook) Marc Chantreux
2020-07-23 8:12 ` Frank Terbeck [this message]
2020-07-23 10:40 ` Jérémy Korwin-Zmijowski
2020-07-23 12:01 ` Marc Chantreux
2020-07-23 14:08 ` Jérémy Korwin-Zmijowski
2020-07-23 19:55 ` Zelphir Kaltstahl
2020-07-23 11:33 ` Marc Chantreux
2020-07-23 15:08 ` a French mailing list (was: test anything? (Re: My Guile Hacker Handbook)) Dmitry Alexandrov
2020-07-23 20:34 ` Marc Chantreux
2020-07-23 10:32 ` My Guile Hacker Handbook Bonface M. K.
2020-07-23 14:09 ` Jérémy Korwin-Zmijowski
2020-07-24 0:58 ` Bonface M. K.
2020-07-24 0:06 ` No Guile on Windows? (was: My Guile Hacker Handbook) Dmitry Alexandrov
2020-07-24 5:41 ` Eli Zaretskii
2020-07-24 7:22 ` Dr. Arne Babenhauserheide
2020-07-24 9:32 ` Christopher Lam
2020-07-24 11:50 ` Mike Gran
2020-07-24 16:25 ` Licensing of Cygwin comatibility layer (was: No Guile on Windows?) Dmitry Alexandrov
2020-07-24 23:33 ` Mike Gran
2020-07-24 14:00 ` No Guile on Windows? Ludovic Courtès
2020-07-24 14:20 ` Stefan Israelsson Tampe
2020-07-24 17:46 ` Dr. Arne Babenhauserheide
2020-07-24 17:47 ` Dmitry Alexandrov
2020-07-24 18:41 ` Jan Wielkiewicz
2020-07-25 3:48 ` No Guile on Windows? (was: My Guile Hacker Handbook) David Pirotte
2020-07-25 6:31 ` Eli Zaretskii
2020-07-25 13:56 ` Christopher Lam
2020-07-25 14:28 ` Eli Zaretskii
2020-07-28 2:52 ` Christopher Lam
2020-07-28 3:57 ` Mike Gran
2020-07-28 6:40 ` Vladimir Zhbanov
2020-07-25 16:49 ` Mike Gran
2020-07-25 16:33 ` Jérémy Korwin-Zmijowski
2020-07-25 21:38 ` No Guile on Windows? Dmitry Alexandrov
2020-07-24 6:47 ` No Guile on Windows? (was: My Guile Hacker Handbook) divoplade
2020-07-24 11:38 ` Stefan Israelsson Tampe
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blk6vedr.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=eiro@phear.org \
--cc=guile-user@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.
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).