The testing framework can always be inserted later. What’s important for the starter task is being able to understand what’s going on in SurveyMan/surveyman.js.
This repository used to live in SurveyMan/SurveyMan, but was split out into its own repository. It implements a subset of the functionality found in SurveyMan/SurveyMan.
What I want to see in the starter task is that you can understand the relationships between the objects. The schemata for the objects live in SurveyMan/Schemata. However, there is a globals file that contains a dump of an example survey.
If there is a testing framework that you like and already know how to use, go ahead and use it. However, if setting up that testing framework requires more knowledge about the system than you currently have, then I would rather see you spend your time showing me that you can read and understand the structure of a Survey object and how the interpreter executes a survey program. For example, don’t worry about mocks for now. Just instantiate examples. You can have something as simple as a set of boolean functions that test invariants. Execute these functions at the end of the file and print out the results. Pushing these functions into a testing framework is something that can be done at a later time.