ars9 9df8a652dc
CI / changes (pull_request) Successful in 7s
CI / version (pull_request) Skipped
CI / server (pull_request) Successful in 1m6s
CI / client (pull_request) Successful in 1m20s
CI / image (pull_request) Skipped
ci: guard image job with an explicit push-event check
- defense in depth alongside the version job's existing push-only
  condition, so the image job can't run on pull requests
2026-10-01 12:29:08 +03:00
2026-10-01 11:44:51 +03:00

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


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.

S
Description
A browser automation and QA service for web applications.
Readme MIT
3.2 MiB
0 Stars 1 Watchers 2 Forks
Languages
TypeScript 93.1%
CSS 5.4%
JavaScript 0.6%
Dockerfile 0.6%
Shell 0.2%