CheckOps
Wokwi
Wokwi is an online and VS Code simulator for ESP32, Arduino, STM32 and other microcontrollers, with Wokwi CI for automated firmware tests in GitHub Actions and GitLab CI.
Latest public signals
Not refreshed yet. Refresh reads the public site and, when the entry has a GitHub repository, the latest release.
Introduction
Wokwi lets you create and simulate digital circuits and microcontroller projects in the browser, including ESP32, Arduino and STM32 boards with virtual parts and virtual WiFi. Paid plans add Wokwi for VS Code and high-performance builds.
For testing, Wokwi’s site describes a solution for automated testing of embedded firmware on CI systems like GitHub Actions and GitLab CI, so firmware can run against simulated hardware on every commit. A Classroom licence serves education.
In the quality loop Wokwi provides hardware-free firmware tests.
Features
- Browser simulator: No hardware needed.
- Many boards: ESP32, Arduino, STM32.
- Virtual WiFi: Network simulation.
- VS Code integration: Simulate locally.
- CI testing: GitHub Actions and GitLab CI.
- Private IoT gateway: On paid plans.
Pros
- Free for open source: Community licence at €0.
Cons
- Proprietary: Closed-source simulator.
- Part coverage: Not every component modelled.
- Seat pricing: Commercial use priced per seat.
Usage and Links (Example)
- Add a Wokwi project configuration and circuit diagram to your firmware repository.
- Simulate locally in VS Code.
- Run the Wokwi CI action with a scenario that checks serial output.
Resources:
Pricing
Wokwi lists Community at €0 for open-source projects, Hobby at €5.6 per month, Hobby+ at €8.1 per month and Wokwi Pro at €20 per seat per month (annual billing).
Recommended for?
- Makers and IoT teams testing ESP32 or Arduino firmware.
Conclusion
Wokwi makes microcontroller simulation accessible and CI-ready.
Validate on real hardware before shipping.
On CheckOps, Wokwi is filed under the Integration testing and Release & CI gates stages. Related tools listed here include Renode, Ceedling, cmocka, Unity Test (C), labgrid and pytest-embedded. A short trial on a real project, with your own code, data and pipeline, is usually the fastest way to choose between them, because fit matters more than feature lists. Facts here come from the official site, documentation and repository, checked on 11 November 2026.
Alternatives
Other tools on CheckOps that cover similar ground. Open a page, or compare one with Wokwi side by side.
RRenodeRenode is Antmicro's MIT-licensed open-source simulation framework that runs unmodified embedded firmware on virtual boards and multi-node networks, with Robot Framework-based testing for CI.Compare with Wokwi
CCeedlingCeedling is an MIT build and test system for C projects from ThrowTheSwitch, combining Unity, CMock and CException for embedded unit testing.Compare with Wokwi
Ccmockacmocka is an Apache-2.0 unit testing framework for C with mock objects that needs only the standard C library, working across platforms including embedded.Compare with Wokwi
UUnity Test (C)Unity is an MIT-licensed unit testing framework for C focused on embedded toolchains, consisting of a single C file and two headers, from ThrowTheSwitch.org alongside CMock and Ceedling.Compare with Wokwi
Llabgridlabgrid is an LGPL-2.1-or-later Python library from Pengutronix for controlling embedded boards in automated tests, with remote access, power and boot control, and a pytest plugin.Compare with Wokwi
Ppytest-embeddedpytest-embedded is Espressif's MIT pytest plugin for embedded testing, with services for serial, ESP-IDF, Arduino, QEMU, Wokwi and JTAG.Compare with Wokwi