vrr/Pulse
2
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-04-28 03:20:11 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
Pulse/tests/integration
History
rcourtman 7c180ea056 Fix integration test data directory permissions 
Root cause: Pulse server was crashing on startup with permission denied when
trying to create .encryption.key file.

The docker-compose test config set PULSE_DATA_DIR=/tmp/pulse-test-data, but
this directory was owned by root (created by Docker volume mount). The
entrypoint script only chowns /data, not /tmp/pulse-test-data.

Solution: Change PULSE_DATA_DIR to /data which is already handled by the
entrypoint script's chown command (line 36 of docker-entrypoint.sh).

This fixes the fatal error:
  failed to get encryption key: failed to save key:
  open /tmp/pulse-test-data/.encryption.key: permission denied

Related to #695
2025-11-12 09:10:30 +00:00
..
mock-github-server Add comprehensive integration test suite for update flow 2025-11-11 09:31:52 +00:00
scripts Add comprehensive integration test suite for update flow 2025-11-11 09:31:52 +00:00
tests Add comprehensive integration test suite for update flow 2025-11-11 09:31:52 +00:00
.gitignore Add integration test package-lock.json to version control 2025-11-12 00:05:45 +00:00
docker-compose.test.yml Fix integration test data directory permissions 2025-11-12 09:10:30 +00:00
IMPLEMENTATION_SUMMARY.md Add comprehensive integration test suite for update flow 2025-11-11 09:31:52 +00:00
package-lock.json Add integration test package-lock.json to version control 2025-11-12 00:05:45 +00:00
package.json Add comprehensive integration test suite for update flow 2025-11-11 09:31:52 +00:00
playwright.config.ts Add comprehensive integration test suite for update flow 2025-11-11 09:31:52 +00:00
QUICK_START.md Add comprehensive integration test suite for update flow 2025-11-11 09:31:52 +00:00
README.md Add comprehensive integration test suite for update flow 2025-11-11 09:31:52 +00:00
tsconfig.json Add comprehensive integration test suite for update flow 2025-11-11 09:31:52 +00:00

README.md

Update Integration Tests

End-to-end tests for the Pulse update flow, validating the entire path from UI to backend.

Architecture

┌─────────────────┐     ┌──────────────────┐     ┌─────────────────────┐
│  Playwright     │────▶│  Pulse Server    │────▶│  Mock GitHub API    │
│  (Browser UI)   │     │  (Test Instance) │     │  (Controlled        │
│                 │     │                  │     │   Responses)        │
└─────────────────┘     └──────────────────┘     └─────────────────────┘

Test Scenarios

  1. Happy Path: Valid checksums, successful update
  2. Bad Checksums: Server rejects update, UI shows error once (not twice)
  3. Rate Limiting: Multiple rapid requests are throttled gracefully
  4. Network Failure: UI retries with exponential backoff
  5. Stale Release: Backend refuses to install flagged releases

Frontend Validation

  • UpdateProgressModal appears exactly once
  • Error messages are user-friendly (not raw API errors)
  • Modal can be dismissed after error
  • No duplicate modals on error

Running Tests

Local Development

# Start test environment
cd tests/integration
docker-compose up -d

# Run tests
npm test

# View logs
docker-compose logs -f pulse-test
docker-compose logs -f mock-github

# Cleanup
docker-compose down -v

CI Pipeline

Tests run automatically on every PR touching update code via .github/workflows/test-updates.yml

Test Data

The mock GitHub server (mock-github-server/) provides controllable responses:

  • /api/releases - List all releases
  • /api/releases/latest - Latest stable release
  • /download/{version}/pulse-{version}-linux-amd64.tar.gz - Release tarballs
  • /download/{version}/checksums.txt - Checksum files

Response behavior can be controlled via environment variables:

  • MOCK_CHECKSUM_ERROR=true - Return invalid checksums
  • MOCK_NETWORK_ERROR=true - Simulate network failures
  • MOCK_RATE_LIMIT=true - Enable aggressive rate limiting
  • MOCK_STALE_RELEASE=true - Mark releases as stale

Success Criteria

  • ✅ Tests run in CI on every PR touching update code
  • ✅ All scenarios pass reliably
  • ✅ Tests catch checksum validation issues automatically
  • ✅ Frontend UX regressions are blocked