I like this idea but I think the design needs to be pretty drastically rethought. Node.js is not really the right medium for this sort of test, although it might function as a first barrier for screening the interested; "you must be able to follow readmes to install software" etc. What I'm more concerned is the idea that this is apparently structured like an automated test. If you used it that way, then here is a fun…
I agree, I also thought it wasn't clear if we were supposed to be writing tests, or code that was to be tested. Instead of modifying the test cases have them fill out a functions file and then run the random tests against those.
My fear with doing that is that if the functions file is separated from the tests file, then it becomes difficult to see at a glance what the function needs to do in order to make the test pass. That said, I agree that what you're supposed to do could be more clear -- would you care to open an issue so we can discuss it on the repo?