Skip to content

Fix browser regression fixtures (#310) - #311

Merged
martin-raden merged 1 commit into
masterfrom
fix/310-browser-test-fixtures
Oct 27, 2026
Merged

martin-raden merged 1 commit into
masterfrom
fix/310-browser-test-fixtures

Conversation

@Alexander-Mitrofanov

Copy link
Copy Markdown
Collaborator

Summary

  • seed numerical browser regressions from explicit test-only RNA inputs instead of the editable GUI examples
  • keep the independent GUI example availability/JSON validation coverage
  • update the prediction CSV assertion for the seed start/end coordinate defaults introduced by gui tweaks #305
  • document the browser-test repair in the ChangeLog

Validation

  • npm test --prefix gui — 29 tests passed
  • python -m py_compile scripts/wasm/test-browser.py
  • git diff --check
  • Chromium with the current GUI and the newest locally available pre-CopomuS WASM bundle passed all prediction, evaluation, archive, cancellation, and session assertions; it reached the expected final mutation-only boundary where that older bundle lacks Pyodide

Fixes #310

@martin-raden
martin-raden merged commit 9b1c915 into master Oct 27, 2026
9 checks passed
@martin-raden
martin-raden deleted the fix/310-browser-test-fixtures branch October 27, 2026 07:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

browser test in github action fails

2 participants