- server and client jobs only run when their directory (or shared root files) changed, via a new changes job using dorny/paths-filter - the version job now checks the registry for an existing image tag of the current package.json version instead of diffing against the previous commit's package.json, so the image job is skipped once that version has already been pushed - the image job tolerates server/client being skipped rather than requiring both to succeed
liqa
A browser automation and QA service for web applications. It stores multi-step browser scenarios, runs them with Playwright in headless Chromium, and keeps their results, logs and artifacts. Scenarios are managed from a web UI, a REST API, or an MCP (Model Context Protocol) server that lets AI agents define, run and debug them.
Quick start
docker compose up -d --build
No configuration is needed: every setting has a default. To override one, copy .env.example to .env and uncomment it.
Everything is served from one container at http://localhost:13000: the UI at /, the REST API at /api/v1, MCP at /mcp, Swagger at /docs. Data is kept in ./data/.
Installation
To install liqa from the published image, without cloning this repo:
curl -fsSL https://git.hq.ars9.space/ars9/liqa/raw/branch/master/scripts/install.sh | bash
This asks for an install directory, a port and a version (latest by default), then writes a compose.yaml and a data/ directory there. Start it with docker compose up -d in that directory.
Overview
| Concept | Description |
|---|---|
| Scenario | An ordered list of steps (async Playwright JS) that run in sequence in one browser. Versioned: every content change creates a new version |
| Run | One execution of a scenario version in an environment, with per-step status and output, logs, and run files (downloads, failure screenshots, Playwright traces) |
| Snippet | Reusable, versioned code called from steps with context.runSnippet("alias") (or "alias@N" for a specific version) |
| Environment | A named set of key/value settings for a deployment target (URLs etc.), read with context.getEnv(key) |
| Credential | Secret data (e.g. a key file and password), assigned to scenarios under an alias and read with context.getCredential(alias) |
| Session | Saved browser state (cookies + localStorage), e.g. kept from a run with "save session" |
Scenarios, snippets, environments and credentials can be exported as YAML and imported back (one file may hold several of them).
Documentation
- docs/architecture.md - components, data model, client
- docs/scenario.md - runs, the script
contextAPI, versioning, import/export, Playwright traces - docs/mcp.md - MCP tool reference
- docs/development.md - setup, configuration, running, testing, linting, Docker
- CHANGELOG.md - release notes
License
MIT © 2026 Andrii Arsenin
Third-party packages keep their own licenses. The Docker image includes all their notices, and the app serves them at /licenses.txt (linked as "Licenses" in the sidebar footer). See docs/development.md.