playwright testing of jupyterlite

[paddymul]

Checks

• I have checked that this enhancement has not already been requested

How would you categorize this request. You can select multiple if not sure

Developer ergonomics (defaults, error messages)

Enhancement Description

I want comprehensive test coverage of jupyterlite. Jupyterlite is a different deployment target that uses pyodide, much like marimo-wasm. do the same types of tests we do in marimo, marimo-wasm (in particularly checking the JS console for errors), jupyterlab, and buckaroo-server.

Pseudo Code Implementation

No response

Prior Art

other non-storybook playwright tests

[paddymul]

@codex write up a plan

[chatgpt-codex-connector]

Summary

• Added a new planning document for comprehensive JupyterLite Playwright coverage, including goals, in-scope/out-of-scope boundaries, and test architecture aligned with existing targets (marimo, wasm, JupyterLab, server). packages/buckaroo-js-core/JUPYTERLITE_PLAYWRIGHT_PLAN.mdL1-L90
• Documented concrete implementation and CI rollout steps (new config/spec/script/docs updates), plus risk mitigations and exit criteria to guide follow-on execution work. packages/buckaroo-js-core/JUPYTERLITE_PLAYWRIGHT_PLAN.mdL100-L135
• Committed changes on branch work (8adc54c) and created a follow-up PR via the PR tool.

Testing

• ⚠️ python - <<'PY' import urllib.request url='https://jupyterlite.readthedocs.io/en/stable/' with urllib.request.urlopen(url, timeout=10) as r: print('status', r.status) print('final_url', r.geturl()) PY (network tunnel/proxy returned 403 Forbidden in this environment)
• ✅ git diff --cached --check

View task →