Add initial device mapping tests #48

New issue

Closed

opened 2026-05-12 00:50:09 -04:00 by JackFrostbyte · 0 comments

JackFrostbyte commented

2026-05-12 00:50:09 -04:00

Owner

Context

The project already has conservative device mapping behavior, which is one of RGB Aura's important safety features.

Before larger refactors, especially future LLM-assisted animation generation work, the device mapping behavior should have tests to prevent regressions.

Scope

Add tests/conftest.py if useful.
Add tests/test_device_mapping.py.
Cover the current expected mapping behavior.
Test that ambiguous or mismatched devices are rejected.
Test that reserved/unused zones remain protected where practical.

Acceptance criteria

Device mapping safety behavior is covered by tests.
Tests do not require real OpenRGB hardware.
Tests can run in CI/local dev without attached devices.
ruff format passes.
ruff check passes.
Test suite passes.

Branch workflow

Base branch:

develop

Suggested work branch:

test/issue-48-device-mapping-tests

Pull request target:

develop

Do not merge directly into main. main should only receive tested release-ready changes from develop.

## Context The project already has conservative device mapping behavior, which is one of RGB Aura's important safety features. Before larger refactors, especially future LLM-assisted animation generation work, the device mapping behavior should have tests to prevent regressions. ## Scope - Add `tests/conftest.py` if useful. - Add `tests/test_device_mapping.py`. - Cover the current expected mapping behavior. - Test that ambiguous or mismatched devices are rejected. - Test that reserved/unused zones remain protected where practical. ## Acceptance criteria - Device mapping safety behavior is covered by tests. - Tests do not require real OpenRGB hardware. - Tests can run in CI/local dev without attached devices. - `ruff format` passes. - `ruff check` passes. - Test suite passes. ## Branch workflow Base branch: `develop` Suggested work branch: `test/issue-48-device-mapping-tests` Pull request target: `develop` Do not merge directly into `main`. `main` should only receive tested release-ready changes from `develop`.

JackFrostbyte added this to the v1.0.1 - Maintenance and startup reliability milestone

2026-05-12 01:02:32 -04:00