Files
liqa/README.md
T
ars9 bba6eb2f94
CI / server (push) Successful in 1m9s
CI / client (push) Successful in 1m23s
CI / version (push) Successful in 6s
CI / image (push) Successful in 2m7s
chore: license the project under mit
- add the mit LICENSE and set license and author in all package.json
  files, plus a license section in the readme
- generate the license notices of all shipped production dependencies
  and node.js in a dockerfile stage and serve them at /licenses.txt,
  linked from the sidebar footer
- keep license files when slimming node_modules in the image
- add oci labels, with the version passed in by ci
- document licensing in the development docs
- bump version to 1.22.2
2026-10-01 11:44:51 +03:00

2.4 KiB

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


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.