⚡ Project management that doesn't become the project. Boards, Gantt charts, and GitHub integration. Self-host it or use Kaneo Cloud.
Browser smoke tests
These Playwright tests run against a disposable, bundled Kaneo instance built
from the current checkout. They exercise real authentication, workspace creation,
persistence after a reload, and authentication after clearing the session cookie.
They also create projects and tasks, persist task edits, and verify that another
workspace member receives edits through a real WebSocket without reloading.
PostgreSQL uses temporary storage; no existing database or root .env is used.
Local run
Requires Node 24, pnpm 12.15.0, and Docker Compose v2.
pnpm --dir tests/e2e install --frozen-lockfile --ignore-scripts
pnpm --dir tests/e2e exec playwright install chromium
docker compose -f tests/e2e/compose.yml up --build --wait --wait-timeout 180
pnpm test:e2e
docker compose -f tests/e2e/compose.yml down --volumes
The test instance binds to http://localhost:18173. Tests create unique synthetic
users and workspaces. Stop the Compose stack after testing, including failed runs;
its temporary database is discarded. The stack's project name is
kaneo-browserstack-e2e; do not run two copies simultaneously on the same machine.
Reports, failure screenshots, and local Playwright traces are stored in .cache/e2e/.
BrowserStack disables native Playwright tracing; use its session recordings for cloud runs.
Dependency security checks
Run the isolated dependency regressions without browsers, Docker, cloud accounts, or Kaneo services:
pnpm --dir tests/e2e test:security
These tests exercise the installed BrowserStack dependency graph: cache-policy reuse and revalidation, redirect credential stripping, and FTP listing parsing. They run separately from Playwright discovery. This workspace carries a local cache-policy patch and an FTP dependency override; see the patch notes before updating either dependency.
BrowserStack Automate
Set BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY in your shell's environment
using the credentials from your BrowserStack account. Keep them out of source
control and command-line arguments. Start the Compose stack with BrowserStack's
local hostname and the HTTPS override so the app, API, cookies, and WebSockets
share the same secure origin. This also requires OpenSSL:
export KANEO_E2E_HOST=bs-local.com
export KANEO_E2E_TLS=true
export COMPOSE_FILE=tests/e2e/compose.yml:tests/e2e/compose.tls.yml
mkdir -p .cache/e2e-tls
openssl req -x509 -newkey rsa:2048 -nodes -days 1 \
-keyout .cache/e2e-tls/key.pem -out .cache/e2e-tls/cert.pem \
-subj '/CN=bs-local.com' -addext 'subjectAltName=DNS:bs-local.com'
docker compose up --build --wait --wait-timeout 180
pnpm test:browserstack
docker compose down --volumes
unset KANEO_E2E_HOST KANEO_E2E_TLS COMPOSE_FILE
BrowserStack rewrites localhost to bs-local.com for WebKit. Configuring that
hostname explicitly avoids mixing the page's origin with a localhost API URL.
The cloud endpoint is https://bs-local.com:18174. The test-only nginx gateway
uses a freshly generated, one-day self-signed certificate; the cloud test contexts
accept it. Certificate files stay outside uploaded reports. HTTPS avoids the HTTP
400 WebSocket handshake failures observed with WebKit through the Local tunnel.
Local Chromium PR runs continue to exercise the plain HTTP deployment.
The realtime test waits for the application's own keepalive before editing, then asserts both the incoming task event and the updated board without reloading.
The SDK starts and stops BrowserStack Local to connect remote browsers to the
disposable instance. tests/e2e/browserstack.yml runs Chrome on Windows 11 and Playwright
WebKit on macOS Sequoia, with one session per platform (two concurrent sessions).
WebKit is an engine compatibility check; this configuration does not test Safari
on a real iPhone. Remove a platform if your plan allows only one parallel session.
Playwright is pinned to 1.62.1, from BrowserStack's supported 1.62 version family;
check their supported versions before upgrading it.
This integration uses Automate only. Test Reporting & Analytics is disabled; Percy and other BrowserStack products are not configured. Session results and videos appear in the Automate dashboard under Kaneo.
GitHub Actions
- Add repository Actions secrets
BROWSERSTACK_USERNAMEandBROWSERSTACK_ACCESS_KEY. - Merge this integration into
main. - Every push to
mainnow runs BrowserStack automatically. To rerun it, open Actions → BrowserStack → Run workflow, selectingmain.
The CI workflow runs the independent Chromium smoke tests job for PRs, including forks, without cloud credentials. It skips that job only for qualifying docs/site-only PRs. BrowserStack runs Chrome on Windows and WebKit on macOS for runtime-relevant main pushes, manual runs on main, and its daily schedule at 05:43 UTC. A main push may skip cloud work only when its complete diff since a proven full validation is runtime-neutral and that validation is less than 24 hours old. Uncertain evidence, manual runs, and scheduled runs execute both engines in full. Cloud runs are serialized to stay within the two-session limit; obsolete PR runs are cancelled.
Both workflows build the checked-out revision, use a disposable database, upload reports for seven days, and tear down the stack even after failure. BrowserStack credentials are passed only to its credential check and cloud test step. No production instance is contacted. Tests use synthetic accounts; invitation setup uses the normal API without sending email because SMTP is not configured.
Chromium smoke tests keeps its display name for external check consumers.
Require ci-result for PR gating; the former browser-result gate is retired.
Workflow edits do not configure GitHub branch rules.
The cloud check runs after merge and does not currently gate releases.
References: