Interesting approach, I can see the benefits of such approach where the md is acting like a Jupyter notebook of some sort. You place the content with documentation and it becomes a self standing unit of test.
I wonder if this can be replicated to other notions where the docs/data needed for test add more value to live with the test
You’re developing that so it would be nice to have the disclosure.
Additionally, I cannot find any obvious examples of what it does, or how it possible relates, and none of the sections seem to offer anything even resembling an example. The entire site seems like a marketing template.
FWIW— if it is similar, or there are examples, you should absolutely put them to the forefront. I literally have no idea what any of the statements/propositions in the pages actually mean.
I remember using it to implement the test suite for a Shakespeare language interpreter. Fun times.
https://en.wikipedia.org/wiki/Test_Anything_Protocol
I wonder if this can be replicated to other notions where the docs/data needed for test add more value to live with the test
PS: I am currently working on Voiden.
Additionally, I cannot find any obvious examples of what it does, or how it possible relates, and none of the sections seem to offer anything even resembling an example. The entire site seems like a marketing template.
FWIW— if it is similar, or there are examples, you should absolutely put them to the forefront. I literally have no idea what any of the statements/propositions in the pages actually mean.