Andrii Arsenin 85a87b5fb2 fix(scenario-logs): fix out-of-order run log persistence
- Add seq column assigned in call order to fix logs racing each other
  as fire-and-forget writes (e.g. a snippet's "started" entry could be
  saved after its "finished" entry)
- Log snippet start/finish/failure via context.runSnippet, matching
  existing step start/pass/fail logging
- Rework Markdown log export to per-entry sections instead of a table
- Version bump: 1.10.0 -> 1.10.1
2026-09-15 13:17:29 +03:00
2026-04-21 18:09:49 +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
No description provided
Readme
1 MiB
Languages
TypeScript 92.7%
CSS 6.6%
Dockerfile 0.3%
JavaScript 0.3%