Live data from Hacker News

A Markdown-based test suite

blogsystem5.substack.com

1–10 of 15 posts

Re: A Markdown-based test suite

#3
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

Re: A Markdown-based test suite

#6

I think you will like https://voiden.md/ - some what similar to what you did here. PS: I am currently working on Voiden.

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.

Re: A Markdown-based test suite

#7

I think you will like https://voiden.md/ - some what similar to what you did here. PS: I am currently working on Voiden.

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 t…

yep editing my comment !

Re: A Markdown-based test suite

#8
Anybody remember "cram"? From about 10 years ago, https://bitheap.org/cram/ basically a markdown syntax (making heavy use of code-blocks) for documenting and writing tests as "shell commands and expected output" (with a bunch of the sharp edges filed off, like line endings and partial matches.) Was particularly good for easy-to-write, easy-to-review tests of unix utilities. (It's the kind of thing that you only stumble on if you've been working with doctests but they don't really fit well for shell/unix stuff...)
Post reply on HN