LucidPlan
login
projects
ui mode
🔗 go to
bewaking
byggsteg
emacs-packages
ggg
hygguile
iter-vitae
jjba23-socials
jointhefreeworld
keuringsdienst
kracht
lucidplan
oculuslambda
orgwebalchemy
pingwing
pop-server
supreme-sexp-system
uberprojekt
veritas
wikimusic
wolk-jjba
title
status
To-do
Work in Progress
In Review
Done
Rejected
type
Task
Bug
Story
Spike
Time Box
priority
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.
submit