You are reading a single comment by @SimonGAndrews and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Hi , thanks @Gordon , I think I can see your structure and general approach: flash/run tests in node on a host, use a board config that specifies test paramaters the relevant tests, structure test scripts in the file system on the host, using a standard test execute method from node around the Espruino CLI tool. All makes good sense.
And your thoughts or collecting various stats, with simple analysis eg comparison of test runs over time/ builds makes sense too. Your approach would allow small test result stats files (eg JSON) to be stored on the host over time, in a boards structure, and analysed with a tool there. A configuration of the relevant stat and measurement function for a board could work.
Lots to think about. But I get your framework and the idea of structuring tests this way now to evolve the whole concept.