unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Taylan Kammer <taylan.kammer@gmail.com>
To: Tomas Volf <~@wolfsden.cz>, 72367@debbugs.gnu.org
Subject: bug#72367: srfi-64: nested group not counted as one test
Date: Mon, 30 Sep 2024 16:42:34 +0200	[thread overview]
Message-ID: <36bb1a5e-b212-4a1d-88dc-c88e16a47182@gmail.com> (raw)
In-Reply-To: <ZqlEWdEDiAp1Sc49@ws>

On 30.07.2024 21:51, Tomas Volf wrote:
> Hello,
>
> I think I found a bug in (srfi srfi-64) module shipped with GNU Guile.
>
> The specification says the following about the count argument to the test-begin
> form:
>
>> The optional count must match the number of test-cases executed by this
>> group. (Nested test groups count as a single test case for this count.)
> Thus I believe that following should *not* call on-bad-count-function.
>
>     (use-modules (srfi srfi-64))
>     (let ((r (test-runner-null)))
>       (test-runner-current r)
>       (test-runner-on-bad-count! r (λ (runner actual-count expected-count)
>                                      (pk (test-runner-group-stack runner))
>                                      (pk actual-count expected-count)))
>       (test-begin "x" 1)
>       (test-begin "y" 3)
>       (test-assert #t)
>       (test-assert #t)
>       (test-assert #t)
>       (test-end)
>       (test-end))
>
> However as we can see it does:
>
>     ;;; (("x"))
>
>     ;;; (3 1)
>
> Have a nice day
> Tomas Volf

Looks like a bug indeed. I believe I was able to fix it in my implementation with this commit:

    https://codeberg.org/taylan/scheme-srfis/commit/c49e367fbf292c6ee66ff435c7daa1f4ae5a47fa

An equivalent fix could be applied to the upstream reference implementation / current Guile implementation.

- Taylan






  reply	other threads:[~2024-09-30 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 19:51 bug#72367: srfi-64: nested group not counted as one test Tomas Volf
2024-09-30 14:42 ` Taylan Kammer [this message]
2024-10-02  4:32   ` Taylan Kammer

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=36bb1a5e-b212-4a1d-88dc-c88e16a47182@gmail.com \
    --to=taylan.kammer@gmail.com \
    --cc=72367@debbugs.gnu.org \
    --cc=~@wolfsden.cz \
    /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).