Skip to main content
Buttons, LEDs, and UART input
Test suites can now drive the board, not just watch it.
  • Buttons. Press, hold, or tap the board’s buttons at an exact point in virtual time.
  • LEDs. Read whether an LED is on or off, without logging it from the firmware.
  • UART input. Send a command to a firmware shell, or raw bytes for a binary protocol, then expect the reply. A wait can now watch a single UART.
The full API is on test.chiplab-cli for CI. chiplab-cli runs a test suite as one CI step, with no agent in the pipeline. The step fails when a test fails, and the run’s artifacts can be kept by the CI. Setup is on Test in CI.Other changes
  • A suite that runs past 5 minutes now fails with test suite timed out after 300s.
  • A failed run keeps the output captured up to the failure. Request the artifacts by name.
  • Steps and nested it calls count as tests of their own.
  • The type definitions are versioned, and each version has its own URL to pin.
  • testsuite_report is the test runner’s own report. Its format is not guaranteed.
Test suites
You can now test firmware with a TypeScript suite and get a pass or fail for each test.A failing test can fail the CI job, so the suite works as a gate on a pull request. The checks you can write are on test, and the workflow edits are on Test in CI.
Last modified on November 2, 2026