Centralize shared DAW developer test tooling #1

New issue

Open

opened 2026-08-11 20:39:21 +02:00 by michael · 0 comments

michael commented

2026-08-11 20:39:21 +02:00

Owner

Goal

Centralize DAW developer tooling that is currently copied across repositories into one public, shared repository.

Initial scope includes the common test helper (helpers.lua) and test runner (run_tests.sh). The repository should become the canonical maintenance point for reusable developer-side tooling that multiple DAW projects need.

Session rationale

The berhtjan 2.1 migration exposed that multiple DAW repositories currently carry different versions of the same test helpers and runner scripts. This creates drift, duplicated maintenance and inconsistent behavior between repositories.

A shared public developer-tool repository was therefore chosen instead of continuing to copy these files independently.

Scope

Establish daw-dev-tools as the public shared repository for reusable DAW developer tooling.
Move/canonicalize helpers.lua.
Move/canonicalize run_tests.sh.
Compare existing copies across DAW repositories and reconcile version differences before declaring the shared versions canonical.
Define a low-friction way for DAW repositories to consume the shared tooling without maintaining divergent local copies.
Document update/upgrade procedure for consuming repositories.
Keep runtime libraries separate: this repository is for developer/build/test tooling, not application runtime dependencies.

Acceptance criteria

Public repository daw-dev-tools exists.
Canonical helpers.lua is available and documented.
Canonical run_tests.sh is available and documented.
Existing divergent DAW copies have been compared and relevant differences reconciled.
At least one DAW repository consumes the centralized tooling successfully.
Lua 5.1 and Lua 5.4 test workflows remain supported where applicable.
Consumer/update workflow is documented.
Repository purpose clearly distinguishes developer tooling from runtime libraries.

Cross-repository impact

Initial consumers include DAW Lua/module repositories that currently carry their own copies of the test helper or runner. Migration of individual repositories should be tracked where concrete changes are required.

## Goal Centralize DAW developer tooling that is currently copied across repositories into one public, shared repository. Initial scope includes the common test helper (`helpers.lua`) and test runner (`run_tests.sh`). The repository should become the canonical maintenance point for reusable developer-side tooling that multiple DAW projects need. ## Session rationale The berhtjan 2.1 migration exposed that multiple DAW repositories currently carry different versions of the same test helpers and runner scripts. This creates drift, duplicated maintenance and inconsistent behavior between repositories. A shared public developer-tool repository was therefore chosen instead of continuing to copy these files independently. ## Scope - Establish `daw-dev-tools` as the public shared repository for reusable DAW developer tooling. - Move/canonicalize `helpers.lua`. - Move/canonicalize `run_tests.sh`. - Compare existing copies across DAW repositories and reconcile version differences before declaring the shared versions canonical. - Define a low-friction way for DAW repositories to consume the shared tooling without maintaining divergent local copies. - Document update/upgrade procedure for consuming repositories. - Keep runtime libraries separate: this repository is for developer/build/test tooling, not application runtime dependencies. ## Acceptance criteria - [ ] Public repository `daw-dev-tools` exists. - [ ] Canonical `helpers.lua` is available and documented. - [ ] Canonical `run_tests.sh` is available and documented. - [ ] Existing divergent DAW copies have been compared and relevant differences reconciled. - [ ] At least one DAW repository consumes the centralized tooling successfully. - [ ] Lua 5.1 and Lua 5.4 test workflows remain supported where applicable. - [ ] Consumer/update workflow is documented. - [ ] Repository purpose clearly distinguishes developer tooling from runtime libraries. ## Cross-repository impact Initial consumers include DAW Lua/module repositories that currently carry their own copies of the test helper or runner. Migration of individual repositories should be tracked where concrete changes are required.

michael added the

coordination/cross-repo

labels