description@jjba23 Hi Josep, I did most of the work on https://package.opendylan.org/testworks/index.html and it looks like you are going in a similar direction. (Testworks has evolved over many years so it has some historical cruft in it.)
In particular, I have been moving toward not requiring tests to be contained inside of suites. Instead, suites are primarily a way to provide shared setup/teardown (fixtures).
The name "#:sut" is a bit obscure. "system under test"? What about "#:actual" ? I also like the "got" vs "want" terminology that the Go people use. But naming is hard and often comes down to personal taste. I like that you use keyword args for this, which I didn't think of doing in Testworks.
Other things that come to mind:
* Conditional tests? e.g. "only run this test on Windows". Just use regular Scheme code?
* I added "tags" to Testworks for filtering, but honestly haven't found them all that useful.
* An extensible way to describe failures, e.g. how two sequences differ.human idveritas-349priority0idbb07de1d-f810-46b2-9396-115b9ca8ccb8