Comment by chrisweekly
Comment by chrisweekly 14 hours ago
Your linked post about test harnesses is outstanding; thanks for sharing!
Comment by chrisweekly 14 hours ago
Your linked post about test harnesses is outstanding; thanks for sharing!
Well, I thought I explained it well. Frankly, I'm shocked that folks don't know what test harnesses are. They are one of the oldest constructs in Software Engineering. In the days of old, we often called them "Unit Tests."
If you want some concrete examples, here you go:
Here's my "Spinner" widget:
https://github.com/RiftValleySoftware/RVS_Spinner
This is the four test harness apps:
https://github.com/RiftValleySoftware/RVS_Spinner/tree/main/...
This is my checkbox widget:
https://github.com/RiftValleySoftware/RVS_Checkbox
Here's the test harness app:
https://github.com/RiftValleySoftware/RVS_Checkbox/tree/main...
There's more, but these should be enough to illustrate the point.
I agree. the only point that I didn't see there is that test harnesses radically improve reproducibility. no, no change directories, set that environment variable, touch that config file, or do any other manual system state manipulation when running your tests.
put it all in the harness. same run every time, modulo races, and a lot less tripping over magic you can't always remember or show to someone else.
I've skimmed the article and still have no clue what you guys are talking about. Is test harness another word for end to end testing?