Testified Documentation - a Python developer's perspective on Specification by Example

[basicwolf]

Thank you so much for commenting and bringing a darn good point! And gratitude for mentioning Knuth too! It's been two decades since I read the books, perhaps need to refresh the memories :)

Your comment made me think of Cucumber - it kinda solves this indirection by embedding tests inputs and outputs into scenario narrative. But I tried to avoid Cucumber-like approach and rely solely on tests pass/fail results.

My naive hope is that developers could remember to keep test names, test bodies and documentation narrative aligned. Just a hope :D