Repository navigation
Check TESTING.md and update test results #74
Description
TESTING.md has many instructions on how to test skills against different models.
It also has a table of "Results for models".
That should be updated before release.
Status review: 2026-10-30
At the October 27 review, #183 was open. #183 merged into main as 29dc5455a84e1553e0682d77073cd67a856fb83d. It addresses the checkout-directory example and the Python-version prerequisite, with reported Python 3.15 unit-test results. It explicitly does not complete the results-table work. Current TESTING.md uses the Harness Test Record, not the old Results for models table, and keeps Cowork/ChatGPT limitations explicit. Coordinate dependency-install wording with #141/#143. Keep this issue open until the intended evidence/results refresh is complete; exact release-host validation remains #60.
Issue audit — 2026-11-02
Completed by merged #183, #217, and #250. TESTING.md now documents Python setup, exact-release Codex verification, and current harness results including Muse, with limitations explicit. The old general results-refresh request is fulfilled. Remaining work stays in #60 (exact bundles across hosts), #105/#106 (cloud traces), #186 (omp workflow evidence), and #252 (Muse routing). Closing this issue does not declare those hosts fully verified.
Activity
[-]Verifying TESTING.md instructions.[/-][+]Verify TESTING.md instructions and update results[/+]maeyako commentedon Oct 27, 2026
Hello! I’m a new contributor and would like to help with this if it’s still open.
I followed TESTING.md from scratch on macOS. The unit tests pass on Python 3.15, but I hit one snag: macOS ships Python 3.9, and with it pytest fails during collection with TypeError: unsupported operand type(s) for |, which doesn’t make the 3.10+ requirement obvious. I also noticed the setup example still refers to egm_opensource as the folder name.
I’d like to improve the setup instructions based on this. For the “update results” part: the “Results for models” table seems to have become the Harness Test Record. Is there still something you’d like contributors to update there, or should I focus on the instructions? Thanks :)
[-]Verify TESTING.md instructions and update results[/-][+]Check TESTING.md and update test results[/+]