2 Commits

Author	SHA1	Message	Date
rcourtman	c728539f07	Restore completed Core E2E verdicts: shard CI, drop release tag from test image ... Every main push since the v6 branch flip was cancelled at the 45-minute job timeout with no verdict. The flip brought the full 94-spec suite onto main (the last green run, 2026-06-29, ran only 2 specs on the v5 main), and it runs sequentially against a release-tagged image whose mock-fixture gate returns 403 without a demo entitlement. Dozens of specs fail, retry twice each, and burn the budget: of the 31 minutes of suite time in run 28907574469, 18.8 minutes were failing attempts. - Add GO_BUILD_TAGS build arg (default release) and build the pulse:test e2e image with it empty, matching the dev harness the suite is green under. Shipped images keep the release tag; release-gate behavior keeps its dedicated -tags release Go tests. - Shard Playwright 4 ways across a CI matrix (214/202/205/203 tests per shard) with per-shard report artifacts and an aggregate verdict job. - Cap CI at 20 failures so an env-broken run reports red in minutes instead of grinding into a no-verdict cancellation.	2026-07-08 08:00:55 +01:00
Claude	2afdca4d30	Add comprehensive integration test suite for update flow ... Implements end-to-end testing infrastructure for the Pulse update flow, validating the entire path from UI to backend with controllable test scenarios. ## What's Included ### Test Infrastructure - Mock GitHub release server (Go) with controllable failure modes - Docker Compose test environment (isolated services) - Playwright test framework with TypeScript - 60+ test cases across 6 test suites - Helper library with 20+ reusable test utilities ### Test Scenarios 1. Happy Path (8 tests) - Valid checksums, successful update flow - Modal appears exactly once - Complete end-to-end validation 2. Bad Checksums (8 tests) - Server rejects invalid checksums - Error shown ONCE (not twice) - fixes v4.28.0 issue type - User-friendly error messages 3. Rate Limiting (9 tests) - Multiple rapid requests throttled gracefully - Proper rate limit headers - Clear error messages 4. Network Failure (10 tests) - Exponential backoff retry logic - Timeout handling - Graceful degradation 5. Stale Release (10 tests) - Backend refuses flagged releases - Informative error messages - Proper rejection logging 6. Frontend Validation (15 tests) - UpdateProgressModal appears exactly once - No duplicate modals on error - User-friendly error messages - Proper accessibility attributes ### CI/CD Integration - GitHub Actions workflow (.github/workflows/test-updates.yml) - Runs on PRs touching update-related code - Separate test runs for each scenario - Regression test to verify v4.28.0 issue prevention - Automatic artifact uploads ### Documentation - README.md: Architecture and overview - QUICK_START.md: Getting started guide - IMPLEMENTATION_SUMMARY.md: Complete implementation details - Helper scripts for setup and test execution ## Success Criteria Met ✅ Tests run in CI on every PR touching update code ✅ All scenarios pass reliably ✅ Tests catch v4.28.0 checksum issue type automatically ✅ Frontend UX regressions are blocked ## Usage ```bash cd tests/integration ./scripts/setup.sh # One-time setup npm test # Run all tests ``` See QUICK_START.md for detailed instructions. Addresses requirements from issue for comprehensive update flow testing with specific focus on preventing duplicate error modals and ensuring checksum validation works correctly.	2025-11-11 09:31:52 +00:00