Skip to main content
Wokwi provides a robust simulation solution for automated testing of your embedded firmware on CI systems like GitHub Actions, GitLab CI, and others. You can use Wokwi to run your tests on every commit, and get instant feedback on your code changes. Behind the scenes, Wokwi CI uses the same simulation engine that powers the Wokwi Simulator. The simulation runs in the cloud, and you can stream the serial output back to your CI system to verify that your firmware behaves as expected.

​
Wokwi in the Loop (WITL)

Wokwi in the Loop (WITL) is a testing methodology that combines the best of both worlds: the speed and convenience of unit testing with the realism of hardware testing. With WITL, you can run your firmware on a simulated hardware platform, interact with the firmware using virtual buttons and sensors, and verify the firmware’s behavior by checking the serial output. For basic testing scenarios, you can use the Wokwi CLI to run your firmware on your local machine or CI system. The CLI allows you to start the simulation, check the serial output, and fail the test if the output does not match the expected value. For more advanced testing scenarios, you can write automation scenarios that automate the simulation, push buttons, change the state of the sensors, and check the serial output.

​
CI Architecture

Wokwi CI is powered by a simulation server that runs in the cloud. The server receives your firmware binary, simulates it, and streams the serial output back to your CI system. The server is stateless and can run multiple simulations in parallel.
Wokwi does not store your firmware, and it is deleted from the cloud server after the simulation is finished. If you do not want to upload your firmware to the cloud, please contact us to discuss options for on-premise deployment of Wokwi CI.

​
Simulation Time and Limits

The simulation time is calculated as the sum of the simulation time of all the tests in your CI workflow. Each user has a limit of simulation time per month, according to their Wokwi plan:
  • Free users: 50 minutes
  • Hobby and Hobby+ users: 200 minutes
  • Pro users: 2000 minutes
For more information about the paid plans, please see the Pricing page. If you need more simulation time, please contact us to discuss options for a custom plan.

​
Limiting Individual Test Time

You can limit the simulation time for each test in your CI workflow using the --timeout option of the CLI. For example, to limit the simulation time to 10 seconds, use: 
wokwi-cli --timeout 10000

​
AI Agent Integration

The Wokwi CLI includes experimental support for the Model Context Protocol (MCP), enabling AI agents to interact with Wokwi’s simulation capabilities. This allows AI assistants to run automated tests, simulate hardware behavior, and integrate Wokwi into AI-powered development workflows.

​
Next Steps

Install the Wokwi CLI

Run your firmware on your local machine or CI system

Write Automation Scenarios

Automate the simulation and test your firmware

Use Wokwi with GitHub Actions

Run your tests on every commit

Set up MCP Support

Integrate Wokwi with AI agents
Check out the example projects that are set up to run on Wokwi CI, or join the Wokwi Discord server to get help and share your projects with the community.

Build docs developers (and LLMs) love

Get started for freeTalk to us