While working #306 I noticed that it might be beneficial for learners to skip single tests, enabling a workflow where learners implement and enable one test after the other (as seen e.g. on the Rust and F# track)
Also skipping all tests by default might improve the overall track setup as executing dune runtest from the track root can serve as a basic sanity check for all exercises and test harnesses.
An example of how this might look like can be found here
brainpower-org/ocaml-exercism-cubicle/acronym/test.ml#L4-L6
I also thought it might be nice to have a CI step that copies examples.ml and runs the (then enabled) unit tests against it. I'm not sure what the best way to do this would be, thoughts?
I tried to contributes this in the test-generator templates but failed to compile the test-generator.
While working #306 I noticed that it might be beneficial for learners to skip single tests, enabling a workflow where learners implement and enable one test after the other (as seen e.g. on the Rust and F# track)
Also skipping all tests by default might improve the overall track setup as executingdune runtestfrom the track root can serve as a basic sanity check for all exercises and test harnesses.An example of how this might look like can be found here
brainpower-org/ocaml-exercism-cubicle/acronym/test.ml#L4-L6
I also thought it might be nice to have a CI step that copiesexamples.mland runs the (then enabled) unit tests against it. I'm not sure what the best way to do this would be, thoughts?I tried to contributes this in the test-generator templates but failed to compile the
test-generator.