Andrii Arsenin 9fb6e8538b feat(runs): record playwright traces with per-run trace mode, bump to 1.15.0
- record a trace for each scenario run and upload it as trace.zip
- add PLAYWRIGHT_TRACE_MODE (on, retain-on-failure, off) as the default
- add a trace mode option to the run modal, stored per run and reused
  by repeat run; expose the default via GET /scenarios/run-defaults
- accept traceMode in POST /scenarios/:id/run and run_scenario MCP tool
- share one run modal component between scenario list and detail pages
- git-ignore server/data
2026-09-30 14:58:07 +03:00

liquio-qa-bot

A headless QA automation service for Liquio environments. Exposes an MCP (Model Context Protocol) server that lets AI agents define, run, and monitor multi-step browser test scenarios using Playwright.


Overview

The bot manages four core concepts:

Concept Description
Environment A named set of URLs for a deployment target (e.g. liquio-diia-stg)
Key A JSON descriptor in keys/ that points to an EDS key file + password
Session Saved browser state (cookies + localStorage) produced by a login
Scenario An ordered list of steps that run in sequence against a shared browser instance

Architecture

See docs/architecture.md.


Key descriptors

See docs/key-descriptors.md.


MCP tools

See docs/mcp.md.


Scenario execution

See docs/scenario.md.


Development

See docs/development.md for setup, running, testing, linting, and Docker instructions.

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%