Verify office editor save-back round-trip end-to-end #147

New issue

Open

opened 2026-04-26 07:47:39 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-26 07:47:39 +00:00

Member

The merged office crate covers open + render + delete + upload but the save-back path is unexercised. OnlyOffice POSTs edits to editorConfig.callbackUrl -> hero_office_server::handle_save_document -> hero_foundry. A regression there silently loses user work and there is no test that would catch it.

Acceptance

E2E spec opens a seeded xlsx, types a value into a known cell, triggers Force-Save (or waits for the auto-save interval), closes the editor, re-opens, asserts the value persisted.
Same shape for docx (text insertion) so we cover both documentType: cell and word.
Spec runs against a live hero_os + hero_office + OnlyOffice stack the same way tests/e2e/office_*.spec.ts already do.

The merged office crate covers open + render + delete + upload but the save-back path is unexercised. OnlyOffice POSTs edits to `editorConfig.callbackUrl` -> `hero_office_server::handle_save_document` -> hero_foundry. A regression there silently loses user work and there is no test that would catch it. ## Acceptance - E2E spec opens a seeded xlsx, types a value into a known cell, triggers Force-Save (or waits for the auto-save interval), closes the editor, re-opens, asserts the value persisted. - Same shape for docx (text insertion) so we cover both `documentType: cell` and `word`. - Spec runs against a live hero_os + hero_office + OnlyOffice stack the same way `tests/e2e/office_*.spec.ts` already do.