You are reading a single comment by @Gordon 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.
@Gordon
That's right, yes...
Over the years I have had several attempts at setting something up, including having a Raspberry Pi that will flash the devices and the run tests on them, but there's never been a massive amount of interest and I've never got to the point of setting something up permanently - the permanent setup I had about 10 years ago failed (and didn't handle nRF52) and I never got around to doing anything new.
This is the latest code if it's any help: https://github.com/espruino/EspruinoTester
Ideally if you could add ESP32 tests and flashing in there, at least there will also be the ability to flash the official boards too.
The idea is we can have several directories of tests - some for generic JS, some for bluetooth, wifi, specific features only on certain devices, etc.
Testing I2C/etc is a bit problematic but the safest is probably to agree on some cheap device that can be written/read (I2C EEPROM/etc) that can be wired up with minimal wires, and those could be added to the hardware. I feel like those are probably not the most important tests anyway though, and generally once working they stay working.
The thing I've always felt was missing was a nice way of displaying the information such that it could be dug into nicely. Not sure if you have any ideas?
Test pass/fail is pretty straightforward, but it's nice to store other stats too (speed+firmware size). In the initial setup I had some benchmarks I ran and there were a few times when I looked at the graph and saw things got slower/bigger, and managed to drill down to the commit and fix it. It's also more of a motivation to improve things as you can actually see it :)