[amar-python]

Tests for the closed and open issues, plus a matrix of which test guards which issue.

What's here

docs/ISSUE_TESTS.md: one row for each of the 69 issues: the test that fails if it comes back, or why there isn't one (decisions, docs, work needing a person or another system). State as of 10 Nov, after M5, M6, M7 and #229 merged.

New tests

File	Guards
tests/system/test_issue_regressions.py	#175 an uploader can't destroy a dataset by uploading (asserts the outcome: the original table and rows survive; the T&E path still needs delete permission) · #178 distinct rows kept (all 31 control characters) · #183 rate-limit identity · #189 T&E error row numbers
tests/unit/test_tooling_issues.py	#130 · #169 · #171 setup.sh keeps the old config · #180 · #181 (wrapper) · #182 bundle stops on a failed download · #194 · #207. The shell tests run the real block cut out of each script
tests/unit/test_oidc_https_jwks.py	#113: https key fetch against a local TLS server, key rotation, the refresh cooldown, untrusted certificate refused. Overlaps tests/system/test_oidc_https.py from #229
tests/unit/test_open_issues.py	#57 SECURITY.md · #60 offline scripts
fe: tenant-isolation.test.tsx, fe: log-step-contract.test.ts	#176 · the response schema must accept every log step the API can emit, and list each once
e2e/ (Playwright, production build)	#187, #188, #176, and the #154 Streamlit screen

I re-introduced the original bug for #171, #175, #178, #181, #182, #183, #189, the T&E delete gate, and the OIDC certificate check, and each test failed.

What the tests found

• Every dynamic import in the React app showed as Failed, twice: once after RV-F7: confirmed header mappings silently ignored (API model has no headerMapping field) #186 (the header_mapping log step, fix(ui): accept the header_mapping log step, so imports no longer show as Failed #223) and again after M5 (version, schema_check, cross_upload_duplicates, fix(ui): accept the log steps M5 added, so dynamic imports stop showing as Failed #231/fix(ui): accept the M5 log steps so versioned uploads don't show as Failed #232). The schema rejected log steps the API had started to send. log-step-contract.test.ts now checks the schema against every step the API's loaders can emit; it failed on main both times. Frontend tests don't run in CI, which is how main stayed red unnoticed.
• RV-F1 (BR-36): browser localStorage history leaks across tenants — pending #154 frontend decision #176 is live. A second tenant on the same browser sees the first one's file names on the import-history page (reproduced in Chromium on the production build). Closed as moot, but it still ships. An expected failure in vitest and in the browser suite.
• RV-S7: SQL test wrapper exits 0 on failed assertions (run_tests.sh) #181 is half done: the Tier S psql calls in evals/runner.py have no ON_ERROR_STOP. Not tested: CI's --strict report fails any skipped or expected-fail pytest test.
• M5 changed RV-S5: upload overwrite and mode-switch bypass delete-permission gate #175's mechanism: a repeated filename is now a new version and overwrite is ignored, so nothing is dropped. The tests were rewritten to guard the outcome.

Running

• pytest tests, npx vitest run: as before. Verified here against PostgreSQL: strict free-tier report 282 passed, 0 skipped; unit and system categories all pass; vitest 176 passed + 1 expected fail.
• New tooling marker: tests that run the repo's real shell scripts need bash, so the Windows job leaves them out; the Linux jobs and local runs include them.
• pytest e2e: not part of the default run (needs Playwright, a build and three local servers; see e2e/README.md). 7 passed, 1 expected fail, stable across repeated runs. Not wired into CI.

https://claude.ai/code/session_011T6Wqi8yaiaYWUVH8C4QAY

---

Generated by Claude Code