In testing the Exercism CLI user experience for our Unison track, I found that the file loading and test running process could create unnecessary friction for newcomers. loading relative test file paths while starting the ucm from the src directory of a given track just increased cognitive load for learners.
With this file structure a user can open the ucm from the exercise directory, make their changes in the .u suffixed files without cding around the directory tree and can re-load the test file without more complicated file paths.
No changes to the unison-test-runner or other elements of the ecosystem are required.
The testing instruction docs and associated config files have been updated to reflect this change.
In testing the Exercism CLI user experience for our Unison track, I found that the file loading and test running process could create unnecessary friction for newcomers.
loading relative test file paths while starting theucmfrom thesrcdirectory of a given track just increased cognitive load for learners.With this file structure a user can open the
ucmfrom the exercise directory, make their changes in the.usuffixed files withoutcding around the directory tree and can re-load the test file without more complicated file paths.