Testing for Ludus #18

New Issue

scott · 2023-12-18T05:59:51Z

scott commented

2023-12-18 05:59:51 +00:00

Related to #8, but much bigger:

Write test cases for Ludus! This will of course often take the form of tests in Ludus. But it will be worthwhile, as I work on the language, to also have test cases that cover a lot of things from outside the language, so that if the language isn't in a fully (or even mostly!) workable state, I can still get feedback on what's working and not.

Since we're not pretty tied to JS—we're targeting the browser in CLJS, and eventually WASM—it makes sense to do the thing in JS. And since CLJS speaks node (not deno, sigh), I think we're probably working with izs's node-tap: https://node-tap.org

Related to #8, but much bigger: Write test cases for Ludus! This will of course often take the form of tests _in_ Ludus. But it will be worthwhile, as I work on the language, to also have test cases that cover a lot of things from outside the language, so that if the language isn't in a fully (or even mostly!) workable state, I can still get feedback on what's working and not. Since we're not pretty tied to JS—we're targeting the browser in CLJS, and eventually WASM—it makes sense to do the thing in JS. And since CLJS speaks node (not deno, sigh), I think we're probably working with izs's `node-tap`: https://node-tap.org

scott added the

enhancement

now

clj

labels 2023-12-18 06:00:27 +00:00

scott commented

2023-12-25 04:41:47 +00:00

#22 stands up a basic test harness. Still lots of work to do there.

scott self-assigned this 2023-12-27 04:18:16 +00:00

scott added this to the 0.2.0 milestone 2024-05-19 19:52:59 +00:00

scott referenced this issue

2024-06-24 15:59:52 +00:00