Quality and Safety

Vorliq Testing

Vorliq uses layered testing so blockchain rules, backend APIs, frontend behavior, mobile export readiness, SDK calls, deployment scripts, and real browser routes are checked from different angles.

Test Layers

Python tests verify blockchain blocks, transactions, wallets, storage, profiles, faucet, lending, exchange, governance, treasury, mining status, registry, and security behavior.
Backend Jest tests verify Node API routes, validation, safe error handling, admin protection, incidents, backups, manifests, heartbeat, faucet, mining, and lifecycle route proxies.
Frontend tests verify React rendering, onboarding, navigation, theme behavior, wallet safety, risk notices, and major page states.
SDK checks build the JavaScript SDK and run a bounded smoke call against safe public endpoints.
Mobile Expo export confirms the Expo app bundles for community testing when mobile code changes.
Playwright E2E tests run Chromium browser checks against the live production app using read-only paths.

Read-Only Production E2E

The Playwright suite intentionally does not claim faucet funds, mine production blocks, create posts, submit exchange offers, create proposals, spend treasury funds, or use a real admin token. It checks public routes, layout, navigation, non-destructive page states, and safe API responses only.

Run Locally

cd blockchain
python -m pytest tests/ -v

cd ../backend
npm test

cd ../frontend
npm test -- --watchAll=false
npm run build

cd ../sdk
npm run build

cd ../e2e
npm install
npx playwright install chromium
npm run e2e

Set E2E_BASE_URL to test another deployed environment. The default is https://vorliq.org.

Playwright Coverage

The browser suite covers public web routes, mobile and desktop overflow checks, mobile drawer behavior, desktop More menu behavior, footer social icon buttons, top logo visibility, Dashboard background guardrails, onboarding skip, theme toggle, wallet safety copy, faucet/mine read-only states, invalid transaction and block detail routes, forum search safety, registry summary, health sections, and safe API smoke endpoints.

Failure screenshots, traces, and the HTML report are generated as artifacts and are not committed to the repository.

CI

GitHub Actions runs blockchain, backend, frontend, and read-only Playwright E2E checks. Deployment only proceeds after the CI workflow succeeds. The production deployment workflow still performs server-side health, backup, incident, heartbeat, and deployment checks.