Sswvechore: smooth wording in rewritten comments

b014014b创建于 3 天前历史提交

文件	最后提交记录	最后更新时间
fixtures	test(scorm): backend tests, e2e suite, frontend reliability + instructor UI - 70+ backend pytest: parsing, extraction security (traversal/symlink/zip-bomb/ XXE), runtime conformance (SCORM 1.2 & 2004), completion->progress, cross-org authz, multi-SCO dedup, instructor results, real authoring-tool packages (Rise './', nested <file>, backslash). Tests skip cleanly when enterprise modules are absent so OSS CI stays green. - Synthetic SCORM package corpus generator - apps/e2e/features/scorm: live e2e (import/track, resume, player, real-tool) - Frontend (apps/web/ee): tab-close keepalive WITH auth (was a silent 401 via sendBeacon), accurate LMSCommit/Finish return values, no-token sign-in notice, save-failure banner, resume indicator, a11y roles - Instructor results table wired into EditScormActivityModal	3 个月前
tests	chore: smooth wording in rewritten comments Fix comma splices and awkward phrasing, restore dropped qualifiers, and stop two comments misquoting UI text.	3 天前
README.md	docs: tidy punctuation and wording Plain punctuation in place of dashes, less filler. No facts, commands or links changed.	4 天前
api.ts	chore: replace em dashes in comments and docstrings Comments only; no runtime strings, UI copy or behavior changed.	4 天前

SCORM e2e

End-to-end coverage of the EE SCORM feature: upload → analyze → import → runtime tracking → resume → instructor reporting, plus a browser smoke of the player.

Requires Enterprise Edition

SCORM is an EE-only feature, so these specs need an EE instance (the default npx learnhouse@latest self-host the suite boots is OSS and has no /scorm routes). Point the suite at a running EE stack instead of booting one:

# From the repo root, in one terminal, start an isolated EE dev stack:
learnhouse dev --ee

# Then, against that instance:
cd apps/e2e
E2E_BASE_URL=http://localhost:3000 \
E2E_ADMIN_EMAIL=<admin email> E2E_ADMIN_PASSWORD=<admin password> \
bun run test features/scorm

The API specs (01, 02) are pure REST and exercise the backend fixes (de-dup import, no total_time double-count, valid 2004 tokens, resume, write-only hygiene, authz, instructor results). The browser spec (03) drives the player UI.

Fixtures

fixtures/*.zip are generated by the synthetic corpus generator:

cd apps/api
uv run python -m src.tests.fixtures.scorm_packages ../apps/e2e/features/scorm/fixtures