Integration tests

[rubenhensen]

There are too many email flows to track manually for every change. We need a test suite to cover these flows and catch regressions.

Flows to cover

Sending

• Send an email to a single recipient
• Send an email to multiple recipients
• Send an email with an attachment
• Send via email (attachment, PGP armored, fallback link)
• Send via cryptify (attachment, PGP armored, fallback link)

Receiving / Decryption

• Download (decrypt) an email sent to a single recipient
• Download (decrypt) an email sent to multiple recipients
• Receive an email with multiple required attributes
• Receive an email with optional attributes (some present, some absent)
• Receive an email with a mix of required and optional attributes
• Fallback decryption via URL
• Fallback decryption via attachment

Edge cases

• Decryption with the wrong identity (should fail gracefully)
• Decryption when one of multiple recipients uses the wrong identity
• Re-trying decryption after a failed Yivi session

Related

• Integration tests postguard-tb-addon#53
• Integration tests postguard-outlook-addon#7

[rubenhensen]

Scoping this for epic encryption4all/postguard#247 (workstream A): phase 1 of this issue = run the existing Playwright suite in CI. The repo already has 15 specs in tests/ (mock PKG at **/pkg/v2/request/start, preview port 4173) that only ever run locally.

Definition of done for phase 1:

• ci.yml job: build → npm run preview → playwright test (chromium is enough to start), trace/screenshot artifacts uploaded on failure
• a test:e2e script in package.json
• a deliberately broken spec fails CI

The full flow matrix in the description stays as phase 2 — most of it belongs to the postguard-e2e harness (real stack) rather than mocked browser tests.

[rubenhensen]

/dobby please pick this up — scope is phase 1 as in my comment above: run the existing 15 Playwright specs in CI (build → preview → playwright test, chromium, artifacts on failure, test:e2e script). Known App limitation: deliver any .github/workflows/ changes as a PR-comment patch and a maintainer will land it on your branch. Part of encryption4all/postguard#247 wave 2.

[dobby-coder]

On it! I'm picking up phase 1 from your comment: wiring CI to build → preview → run the 15 existing Playwright specs on chromium via test:e2e, with failure artifacts uploaded.

Since I can't land .github/workflows/ changes directly, I'll deliver that part as a patch in a PR comment for a maintainer to apply — everything else I'll push as normal. I'll follow up once there's something to look at.

[dobby-coder]

Picked this up — #329 is signed off and out of draft, waiting on you.

Ran the gate checks (10 rules + the ci.yml patch you'll need to apply from the PR comment). Found one nit: CLAUDE.md claimed the E2E Tests CI job already existed as a present-tense fact, which would mislead a future agent into skipping local e2e runs. Fixed that myself in e719e45 to describe it as pending. Everything else — commit title, Refs #44 correctly keeping the issue open, reviewer, prose — came back clean. I also reviewed the ci.yml patch itself line by line (action versions, if: failure() placement, artifact paths, no unguarded shell pipes) since a diff review alone wouldn't catch issues there — it looks solid.

Only thing left: apply the ci.yml patch from the PR comment to actually land the E2E Tests job. All 8 existing CI checks are green on the current head.