Write NUnit tests once. Run them on Windows and a Crestron Home processor

Description and use

Developers can write NUnit tests once and run them on both Windows and Crestron Home processors, leveraging packaging, deployment, live and UI testing, and CI integration.

Problem

Developers need to verify that NUnit tests written on a Windows machine behave correctly on a Crestron Home processor, which has different filesystem, networking, and runtime constraints.

Outcome

Developers can run the same NUnit tests on both Windows and Crestron Home processors, ensuring platform compatibility, enabling live and UI tests, and integrating with CI pipelines without duplicating test code.

Workflow

• 1. Write ordinary NUnit tests in a .NET project.
• 2. Use CrestronHomeNUnit.TestAdapter to add a Visual Studio Test Explorer entry that builds a processor test package.
• 3. Deploy the package to the processor via CrestronHomeDevTools or the Windows runner.
• 4. Run the tests on the processor using the Windows runner or the Home tile.
• 5. (Optional) Enable live tests with environment‑specific settings in LiveTestSettings.json.
• 6. (Optional) Add CI steps with GitHub Actions to run hardware stages on a self‑hosted Windows runner.
• 7. (Optional) Perform UI tests against the Crestron Home Android app using the provided UI automation library and Android emulator.

Evidence

The central idea behind CrestronHomeNUnit is straightforward: write the NUnit tests once, and run those identical tests on Windows and on the Crestron Home processor.

Source

The processor package targets .NET Framework 4.7.2 and executes under the processor’s Mono runtime. The desktop tooling uses .NET 10.

Source

For GitHub Actions, a self-hosted Windows runner with network access to the processor can execute the hardware stages.

Source