commit 9775b48a459159d628bb9555f0d380aa2d96f495
parent 63b4ae354143ac6141721787bc3af77438875d9e
Author: triesap <tyson@radroots.org>
Date: Sun, 11 Oct 2026 21:09:08 +0000
web: control successful reply fixture clock (HCP-147)
- Stabilize the successful reply reservation with the existing fixed clock.
- Report terminal reply failures with fixture diagnostics immediately.
- Preserve real second-boundary rejection and paired delivery assertions.
- Retain the failed attempt and require fresh committed verification.
Diffstat:
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/web/tests/e2e/reply-composer.spec.ts b/web/tests/e2e/reply-composer.spec.ts
@@ -474,13 +474,23 @@ test('explicit Send creates an actual self-first paired reply with the authentic
}) => {
await ready(page);
await composer(page).getByLabel('Reply', { exact: true }).fill(sentinel);
+ // This case qualifies successful delivery. The production scenarios above
+ // separately require rejection when the real clock crosses a second.
+ await page.evaluate(() => window.hcp104Fixture.configureSendClock(false));
const before = await page.evaluate(() => window.hcp104Fixture.delta());
await composer(page)
.getByRole('button', { name: 'Send reply', exact: true })
.click();
await expect
- .poll(() => page.evaluate(() => window.hcp104Fixture.snapshot()?.state))
- .toBe('completed');
+ .poll(() => page.evaluate(() => window.hcp104Fixture.snapshot()?.busy))
+ .toBe(false);
+ const terminal = await page.evaluate(async () => ({
+ snapshot: window.hcp104Fixture.snapshot(),
+ diagnostic: await window.hcp104Fixture.diagnostic()
+ }));
+ expect(terminal, JSON.stringify(terminal)).toMatchObject({
+ snapshot: { state: 'completed', busy: false }
+ });
expect(events).toHaveLength(2);
expect(
events.every((frame) => (frame[1] as { kind: number }).kind === 1059)