I think this should be all the asserts/features I need. I have a rough implementation for those but it is not yet working correctly.
Why did you decide on the json based format for test cases? Wouldn't javascript files be better for editing/linting/syntax highlighting?
Maybe a library that provides asserts and an easy way to setup the emulator for running testcases for a single app? Or the other way round, the test code is a module and apptests.js iterates over the exports which are test functions and handles the environment like now.
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.
I've had a play around porting the first of the test cases to json:
https://gist.github.com/halemmerich/3d0f1d41d8eebe76eedc8553530e5dd5
I think this should be all the asserts/features I need. I have a rough implementation for those but it is not yet working correctly.
Why did you decide on the json based format for test cases? Wouldn't javascript files be better for editing/linting/syntax highlighting?
Maybe a library that provides asserts and an easy way to setup the emulator for running testcases for a single app? Or the other way round, the test code is a module and
apptests.js
iterates over the exports which are test functions and handles the environment like now.