Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 15:12 UTC)
Re: Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 15:15 UTC)
Re: Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 17:13 UTC)
Re: Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 17:25 UTC)
Re: Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 18:48 UTC)
Re: Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 19:28 UTC)
Re: Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 20:01 UTC)
Re: Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 20:22 UTC)
Re: Gathering comprehensive SRFI test suites in one place Per Bothner (26 Jan 2020 19:33 UTC)
Re: Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 19:49 UTC)
Re: Gathering comprehensive SRFI test suites in one place Per Bothner (26 Jan 2020 20:03 UTC)
Re: Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 20:11 UTC)
Re: Gathering comprehensive SRFI test suites in one place Per Bothner (26 Jan 2020 20:22 UTC)
Re: Gathering comprehensive SRFI test suites in one place Lassi Kortela (26 Jan 2020 20:31 UTC)
Re: Gathering comprehensive SRFI test suites in one place Arthur A. Gleckler (26 Jan 2020 17:50 UTC)

Re: Gathering comprehensive SRFI test suites in one place Per Bothner 26 Jan 2020 20:02 UTC

On 1/26/20 11:49 AM, Lassi Kortela wrote:
> Thanks for chiming in and explaining your SRFI, Per. Do you have many existing tests for SRFIs in Kawa using the 64 framework? If so, those could be a useful starting point for a portable collection.
>
>> Typical output on Kawa:
>>
>> $ ../bin/kawa  "./lib-test.scm"
>> %%%% Starting test libs  (Writing full log to "libs.log")
>> # of expected passes      269
>> # of expected failures    9
>
> This matches the output I get on various Schemes.

> I guess Peter and I expected the output to explicitly say that all tests have produced the expected result and that's what confused us.

There are no (unexpected) failures reported (individually or in the summary),
so it is implied.

The output can be trivially changed (in %test-final-report-simple
if modifying the sample implementation).

Perhaps something like the following (when all is as expected):

Testsuite libs success (269 tests pass, 9 tests fail as expected)

--
	--Per Bothner
xxxxxx@bothner.com   http://per.bothner.com/