- snapshot scenario and snippet content into version tables on every
content change; live tables keep holding the latest version
- record the scenario version on each run and copy its steps into the
run steps, so runs execute and show the version they were created with
- keep run step history when a step is deleted (FK set null)
- pin a snippet version with runSnippet('alias@N')
- add version picker to the run modal and version info across the UI
- add version list/get endpoints and MCP tools
- include version in exports and require it on import, restoring the
exact version by id + version
162 lines
7.5 KiB
Markdown
162 lines
7.5 KiB
Markdown
# Changelog
|
|
|
|
All notable changes to this project will be documented in this file.
|
|
|
|
## 1.16.0 - 2026-09-30
|
|
|
|
Changes since 1.15.0:
|
|
|
|
### Added
|
|
|
|
- Scenarios and snippets are now versioned, starting at version 1. A scenario's version goes up when its name, description, default environment, timeout or steps change; a snippet's when its alias, title, description or code changes. Saving without changes does not create a new version. Credential assignments and scenario files are not versioned.
|
|
- Each run records the scenario version it runs. The run modal has a version picker (latest by default), `POST /scenarios/:id/run` and the `run_scenario` MCP tool accept an optional `version`, and "Repeat run" reuses the run's version.
|
|
- `context.runSnippet("alias@N")` pins version N of a snippet; `runSnippet("alias")` keeps using the latest. The scenario page's "Used Snippets" section shows which snippets are pinned.
|
|
- Version numbers are shown on the scenario, snippet and run pages and in the scenario and run lists.
|
|
- Added `GET /scenarios/:id/versions[/:version]` and `GET /snippets/:id/versions[/:version]`, and the `list_scenario_versions`, `get_scenario_version`, `list_snippet_versions` and `get_snippet_version` MCP tools.
|
|
- Scenario and snippet exports accept `?version=N` (the `export_scenario` MCP tool takes `version`).
|
|
|
|
### Changed
|
|
|
|
- **Breaking:** scenario and snippet exports now include `version`, and imports require it. An import restores that exact version by id + version: an existing version is left untouched, and a new one is stored under its number and becomes the latest when it is higher than the current latest. Export files from earlier releases need a `version` field added before they can be imported.
|
|
- Scenario exports now include scenario and step timeouts.
|
|
- Runs keep their own copy of the steps they were created with. Editing or deleting a step no longer changes past runs, and deleting a step no longer deletes its results from past runs. Existing run steps are backfilled from the current steps on startup.
|
|
|
|
## 1.15.0 - 2026-09-30
|
|
|
|
Changes since 1.14.0:
|
|
|
|
### Added
|
|
|
|
- Scenario runs now record a Playwright trace (screenshots and DOM snapshots) and upload it to the run's files as `trace.zip` when the run finishes. Open it with `npx playwright show-trace trace.zip` or at https://trace.playwright.dev.
|
|
- Added the `PLAYWRIGHT_TRACE_MODE` setting (`on` (default), `retain-on-failure`, or `off`) that controls which traces are kept.
|
|
- Added a "Playwright trace" option to the run modal to override the trace mode for a single run. It defaults to the server's `PLAYWRIGHT_TRACE_MODE`, served by the new `GET /scenarios/run-defaults` endpoint.
|
|
- `POST /scenarios/:id/run` and the `run_scenario` MCP tool accept an optional `traceMode`. The trace mode is stored on the run, shown on the run detail page, and reused by "Repeat run".
|
|
|
|
### Changed
|
|
|
|
- The run modals on the scenario list and scenario detail pages now share one component.
|
|
- `server/data/` is now git-ignored.
|
|
|
|
## 1.14.0 - 2026-09-30
|
|
|
|
Changes since 1.13.0:
|
|
|
|
### Added
|
|
|
|
- Added a "Repeat run" button on the scenario run detail page that starts a new run of the same scenario with the same environment and "save session" setting, then navigates to it. The button is disabled when the run's environment has since been deleted.
|
|
|
|
## 1.13.0 - 2026-09-30
|
|
|
|
Changes since 1.12.0:
|
|
|
|
### Added
|
|
|
|
- Added credential CRUD tools to the MCP server: `list_credentials`, `get_credential`, `create_credential`, `update_credential`, and `delete_credential`. Combined with the existing `add_scenario_credential` tool, credentials can now be created and attached to scenarios entirely via MCP.
|
|
|
|
## 1.12.0 - 2026-09-16
|
|
|
|
Changes since 1.11.0:
|
|
|
|
### Added
|
|
|
|
- When a scenario or snippet step fails, a full-page screenshot and the current page HTML are captured and uploaded as run artifacts, so failures can be diagnosed from the run's file list.
|
|
|
|
## 1.11.0 - 2026-09-15
|
|
|
|
Changes since 1.10.1:
|
|
|
|
### Added
|
|
|
|
- Added export of a scenario as a standalone, plug-and-play Playwright e2e test project (zip archive with `package.json`, `playwright.config.ts`, `test.spec.ts`, `README.md`, `.env`, `credentials.json`, `snippets/*.js`, and any attached scenario files) that runs entirely independently of the liqa backend. Available as a "Export e2e test" button on the scenario detail page, `GET /scenarios/:id/export-e2e`, and the `export_e2e_test` MCP tool.
|
|
- The exported test only bundles the credentials, snippets, and attached files actually referenced (directly or transitively) by the scenario's steps.
|
|
- Added a "Used Snippets" section on the scenario detail page listing the snippets referenced by the scenario's steps, linking to each snippet's detail page. Backed by `GET /scenarios/:id/used-snippets`.
|
|
|
|
## 1.10.1 - 2026-09-15
|
|
|
|
Changes since 1.10.0:
|
|
|
|
### Added
|
|
|
|
- `context.runSnippet()` now logs "Snippet started"/"finished"/"failed" entries, matching the automatic step start/pass/fail logging.
|
|
|
|
### Changed
|
|
|
|
- Reworked the Markdown log export format: each log entry is now its own `## [level] timestamp` section with the message as its body, instead of a single large table.
|
|
|
|
### Fixed
|
|
|
|
- Run logs could persist out of call order (e.g. a snippet's "started" log appearing after its "finished" log) because writes were fire-and-forget and raced against each other. Log entries now carry a per-run sequence number assigned in call order, and queries/exports sort by it.
|
|
|
|
## 1.10.0 - 2026-09-15
|
|
|
|
Changes since 1.9.1:
|
|
|
|
### Added
|
|
|
|
- Added a "Download logs" button on the scenario run detail page: opens a modal to choose Markdown (default) or CSV, then downloads the run's logs in that format.
|
|
- Added `GET /scenarios/:id/run/:runId/logs/export?format=csv|md` backend endpoint to export a run's logs.
|
|
|
|
## 1.9.1 - 2026-09-15
|
|
|
|
Changes since 1.9.0:
|
|
|
|
### Added
|
|
|
|
- Scenario run logs now include an automatic entry when a step starts and when it finishes (pass or fail), so step boundaries are visible in run logs even for steps that don't call `context.log`/`context.assert` themselves.
|
|
|
|
## 1.9.0 - 2026-09-15
|
|
|
|
Changes since 1.8.0:
|
|
|
|
### Added
|
|
|
|
- Added `context.assert(fn, description)` for scenario/snippet script steps: runs the given function, requires it to return `true`, logs the outcome (`log` on success, `error` on failure or exception), and throws to stop the step on failure.
|
|
|
|
### Changed
|
|
|
|
- Documented `context.assert` in `docs/scenario.md`.
|
|
|
|
## 1.8.0 - 2026-09-15
|
|
|
|
Changes since 1.7.1:
|
|
|
|
### Added
|
|
|
|
- `context.downloadFile()` now accepts `data:` URIs, so scenario steps can save in-script generated content (e.g. a credential JWT) as a run artifact without a network fetch.
|
|
|
|
### Changed
|
|
|
|
- Documented the full scenario step `context` file API (`getScenarioFiles`, `downloadFile`) in `docs/scenario.md`.
|
|
|
|
## 1.7.1 - 2026-04-21
|
|
|
|
Changes since 1.7.0:
|
|
|
|
### Added
|
|
|
|
- Added MCP tools to upload, list, and fetch scenario files using base64 content payloads.
|
|
- Added MCP tools to list run artifacts and fetch run artifact content with metadata.
|
|
|
|
### Changed
|
|
|
|
- Documented MCP binary content handling for scenario files and run artifacts.
|
|
|
|
## 1.7.0 - 2026-04-21
|
|
|
|
Changes since 1.6.1:
|
|
|
|
### Added
|
|
|
|
- Added scenario file storage and run artifact support on the backend.
|
|
- Added file management UI for scenarios and run details, including artifact lists.
|
|
- Added snippet CRUD tools to the MCP server.
|
|
|
|
### Changed
|
|
|
|
- Added dynamic page titles based on the active client content.
|
|
- Extended the scenarios list to show the latest run status and timestamp.
|
|
|
|
### Fixed
|
|
|
|
- Exposed file expiry metadata in scenario and run file responses.
|
|
- Disabled expired download actions in the UI while keeping the action visible. |