Summary
Verified: andremun/InstanceSpace has no CI at all. .github/ contains only an
ISSUE_TEMPLATE/ folder — no workflows/ directory, no automated test run on push or PR.
test_integration.m (the exhaustive option-coverage regression suite) and example.m currently
have to be run manually and trusted before merging. This is a bigger gap than anything found in
the Python port's own testing audit, which already has validation-tests.yml.
Proposed change
Add .github/workflows/tests.yml (or similar), triggered on push/PR to main/development/
*-candidate branches (matching the Python port's branch trigger pattern): set up MATLAB (e.g.
via matlab-actions/setup-matlab), run test_integration.m and example.m, fail the build on
any individual test-case failure or a non-EOF:SUCCESS sentinel, and archive generated outputs/
logs as workflow artifacts to help debug failures.
Motivation
Mirrors what the Python port already has. Without this, every change — including both issues in
this repo's own batch 1 and batch 2 — relies entirely on a human remembering to run the suite
locally before merging, with no gate catching a regression that slips through.
Acceptance criteria
Part of the v0.9.1 milestone. Source: Python-port testing-infrastructure audit (§7), surfaced while examining how the Python port validates against MATLAB. Independent of batches 1 and 2. Suggested order: before #35 (whose longer-term follow-on depends on CI existing).
Summary
Verified:
andremun/InstanceSpacehas no CI at all..github/contains only anISSUE_TEMPLATE/folder — noworkflows/directory, no automated test run on push or PR.test_integration.m(the exhaustive option-coverage regression suite) andexample.mcurrentlyhave to be run manually and trusted before merging. This is a bigger gap than anything found in
the Python port's own testing audit, which already has
validation-tests.yml.Proposed change
Add
.github/workflows/tests.yml(or similar), triggered on push/PR tomain/development/*-candidatebranches (matching the Python port's branch trigger pattern): set up MATLAB (e.g.via
matlab-actions/setup-matlab), runtest_integration.mandexample.m, fail the build onany individual test-case failure or a non-
EOF:SUCCESSsentinel, and archive generated outputs/logs as workflow artifacts to help debug failures.
Motivation
Mirrors what the Python port already has. Without this, every change — including both issues in
this repo's own batch 1 and batch 2 — relies entirely on a human remembering to run the suite
locally before merging, with no gate catching a regression that slips through.
Acceptance criteria
.github/workflows/created with a working test workflowtest_integration.mandexample.magainst the reference datasetEOF:SUCCESS, or any individualtry/catch-wrapped test-case failure in
test_integration.m)Part of the
v0.9.1milestone. Source: Python-port testing-infrastructure audit (§7), surfaced while examining how the Python port validates against MATLAB. Independent of batches 1 and 2. Suggested order: before #35 (whose longer-term follow-on depends on CI existing).