Hardware tests

hw-test runs repeatable tests against real Analog Devices hardware. It works from a developer shell or from CI, and it shares a pool of boards safely between teams. You ask for a board by its capabilities; hw-test finds a compatible free board, runs your test, and releases it.

What do you want to do?

• Run a test on a board that is already set up -> Run a test.

• Write a new test for a supported platform -> Write a test.

• Add my board or fixture to the shared pool -> Integrate hardware.

• Run hardware tests from CI -> Run tests in CI.

• Set up a new hardware host for my team -> Set up a hardware host.

New here?

hw-test is built on Labgrid, but you do not need to learn it to run or write a test. If you want the see the design first, read How hw-test works. When you meet an unfamiliar term, the glossary can help.

Reference and troubleshooting

The reference section covers the hardware model, the client API, the glossary, and troubleshooting. The complete Labgrid documentation is useful when you need options beyond the workflows here.

• How hw-test works

  The mental model behind hw-test in a few minutes.

• Run a test

  Run one existing hardware test from your shell.

• Write a test

  A practical guide to writing and trying a hardware test with hw-test.

• Integrate hardware

  Bring a board or test fixture into the shared hw-test infrastructure.

• Register a board

  Detailed commands for registering a board or fixture with hw-test.

• Run tests in CI

  Run hw-test from a GitHub Actions workflow.

• Set up a hardware host

  How to prepare a hardware host for hw-test.

• Reference

  Reference material for hw-test hardware connections and APIs.