Hi , in the context of testing out a new build of Espruino such as the ESP c3 and how to approach this.
1) I stumbled across the Espruino/test directory in github , and testing with ./Espruino --test,
But it looks like this is for running in a linux build of Espruino only. Is that correct ??
2) is there an approach to structuring tests for a new build? I suppose:
it would be useful to have tests that can be repeated, particularly incases where the build may well go thru further iterations (eg IDF 4.x , idf5.x).
tests will be exercising hardware and peripherals, so will need to have board connection, i2c devices , network etc.
maybe at the at least structuring some simple JS scripts with documented and simple connection setup that can be repeated for a family of devices.
Any thoughts on this. I May make a stab at it for the ESP C3 build .
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 , in the context of testing out a new build of Espruino such as the ESP c3 and how to approach this.
1) I stumbled across the Espruino/test directory in github , and testing with ./Espruino --test,
But it looks like this is for running in a linux build of Espruino only. Is that correct ??
2) is there an approach to structuring tests for a new build? I suppose:
Any thoughts on this. I May make a stab at it for the ESP C3 build .