c0fe15dc01
CI / changes (push) Successful in 4s
CI / server (push) Failing after 1h44m8s
CI / client (push) Successful in 1m52s
CI / image (push) Skipped
Keep test output quiet with opt-in diagnostic logs (#25)
Test runs stay quiet by default. Diagnostic logs can be enabled explicitly when troubleshooting, while normal application logging and saved scenario output remain available.

Resolves #22.

---------

Co-authored-by: ars9 <ars9@pm.me>
Co-authored-by: agent <agent@halstation.halstation.local>
Reviewed-on: #25
Co-authored-by: agent-codex <agent-codex@ars9.space>
2026-11-11 22:23:44 +02:00
2026-10-08 18:54:34 +03:00
2026-10-01 11:44:51 +03:00
2026-10-08 18:54:34 +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.

Authentication is disabled by default. To enable operator-managed accounts, set AUTH_ENABLED=true and provide a private AUTH_JWT_SECRET; then rebuild/restart the service and provision an account with the CLI. See operator authentication for setup and browser/API usage. Existing deployments remain unauthenticated until explicitly enabled.

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/.

To see it work, import and run the self-test example: a scenario that tests liqa itself using an environment, a credential and snippets.


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%