QA Testing

What did you change? Start here.

Level 1: Unit Tests (~3 seconds)

bash
1make test

Run after every change. No excuses.

Level 2: E2E Tests (~5 minutes)

bash
1# CRITICAL: Kill any running dev server first — E2E uses its own database
2lsof -ti :3000 | xargs kill -9 2>/dev/null
3make test-e2e

Playwright tests that run onboarding, create websites, check dashboards, ingest events. Run after features or big changes.

Level 3: Visual QA with agent-browser

For verifying UI rendering, checking that data displays correctly, or testing flows that E2E doesn't cover.

Setup (one-time)

bash
1npm i -g agent-browser
2agent-browser install

Start dev server

bash
1make dev    # MUST use make dev (Go + Vite together)

Dev credentials

• Email: admin@example.com
• Password: password
• Created by make db-seed

Login

bash
1agent-browser open "http://localhost:3000/login"
2agent-browser snapshot -i
3agent-browser fill @e1 "admin@example.com"
4agent-browser fill @e3 "password"
5agent-browser click @e4

Navigate and verify

bash
1agent-browser snapshot -i           # list interactive elements with refs
2agent-browser click @e11            # click element by ref
3agent-browser scroll down 1000      # scroll to find sections
4agent-browser screenshot            # capture page as PNG
5agent-browser get url               # check current URL

Generate real browser events

bash
1# The /_demo page includes the tracking script — fires real pageviews
2agent-browser open "http://localhost:3000/_demo"
3
4# Wait for event processing (~10s), then check dashboard

Key pages to verify

Important

• Always make dev — make watch-go alone won't render Inertia pages
• Click through the UI — don't force navigation with open after login (breaks Inertia state)
• /_demo for real events — sends actual Sec-CH-UA headers from the browser
• Dev database: storage/fusionaly-development.db

Level 4: VM Install Test

Only needed when changing: install script, matcha, Docker setup, or release infrastructure.

Create fresh VM

bash
1multipass delete fusionaly-test --purge 2>/dev/null || true
2multipass launch 24.04 --name fusionaly-test --cpus 2 --memory 2G --disk 10G

Run install

bash
1multipass exec fusionaly-test -- bash -c '
2sudo apt-get update -qq && sudo apt-get install -y -qq expect
3
4cat > /tmp/run_install.exp << '\''EXPECTSCRIPT'\''
5#!/usr/bin/expect -f
6set timeout 300
7spawn sudo bash -c "curl -fsSL https://fusionaly.com/install | bash"
8expect "Enter your domain name"
9send "test.local\r"
10expect "Proceed with this configuration"
11send "Y\r"
12expect eof
13EXPECTSCRIPT
14
15expect /tmp/run_install.exp
16'

Verify

bash
1multipass exec fusionaly-test -- bash -c '
2echo "=== Containers ===" && sudo docker ps
3echo "=== Version ===" && fusionaly version
4echo "=== Health ===" && curl -s http://172.18.0.2:8080/_health
5'

Browser test via tunnel

bash
1VM_IP=$(multipass info fusionaly-test | grep IPv4 | awk '{print $2}')
2ssh -L 8080:172.18.0.2:8080 ubuntu@$VM_IP
3# Open http://localhost:8080/setup

Cleanup

bash
1multipass delete fusionaly-test --purge

Release Checklist

Before tagging a release:

• make test passes
• make test-e2e passes (kill dev server first!)
• Visual QA: dashboard loads, browser stats correct, events ingesting
• VM install test (if install/infra changed)
• Pro: update OSS submodule, build, test

Common Issues