Compare commits

...
5 Commits
Author SHA1 Message Date
ars9 75bb0af9fd chore: self-test example and tag-only image builds
CI / server (push) Successful in 1m7s
CI / changes (push) Skipped
CI / client (push) Successful in 1m15s
CI / image (push) Successful in 1m58s
- examples/self-test: importable scenario, snippets, credential and
  environment that test the liqa instance they run on
- CI builds the Docker image only for vX.Y.Z release tags
- bump version to 1.24.3
2026-10-02 15:43:31 +03:00
ars9 0c11e11c27 Merge pull request 'feat(examples): add self-test example' (#10) from feat/examples into master
CI / changes (push) Successful in 6s
CI / client (push) Skipped
CI / server (push) Successful in 1m6s
CI / image (push) Skipped
Reviewed-on: #10
2026-10-02 15:42:19 +03:00
ars9 c1924060eb feat(examples): add self-test example
CI / changes (pull_request) Successful in 7s
CI / client (pull_request) Skipped
CI / server (pull_request) Successful in 1m7s
CI / image (pull_request) Skipped
- add examples/ with a ready-to-import self-test: environment, credential,
  snippets and a scenario that creates, runs and checks another scenario
  through the liqa REST API and UI, then cleans up
- add test/examples.spec.ts: imports every example and parses its code
- link the examples from README, docs/scenario.md and CLAUDE.md

Closes #6
2026-10-02 15:39:02 +03:00
ars9 28dfce246a Merge pull request 'ci: build docker images only on release tags' (#9) from chore/release-on-tags into master
CI / changes (push) Successful in 7s
CI / server (push) Successful in 1m12s
CI / client (push) Successful in 1m21s
CI / image (push) Skipped
Reviewed-on: #9
2026-10-02 14:37:34 +03:00
ars9 a0624789ce ci: build docker images only on release tags
CI / changes (pull_request) Successful in 6s
CI / server (pull_request) Successful in 1m19s
CI / client (pull_request) Successful in 1m26s
CI / image (pull_request) Skipped
- trigger the image job on vX.Y.Z tag pushes instead of master pushes
- run server and client checks unconditionally on tags before the build
- fail the build when the tag doesn't match the package.json version
- document the release routine: version bump, changelog and tag are
  done on master after work branches are merged
2026-10-02 14:36:59 +03:00
12 changed files with 489 additions and 60 deletions

No files matched your search

+23 -41
View File
@@ -1,9 +1,8 @@
# Code quality checks on master and pull requests. The server and client jobs
# only run when their directory (or shared root files) changed. On a push to
# master, also builds the Docker image and pushes it to this Gitea instance's
# container registry, tagged with the root package.json version and `latest`
# - unless that version's image already exists in the registry, in which case
# the push is skipped.
# only run when their directory (or shared root files) changed. On a release
# tag push (vX.Y.Z), runs both jobs unconditionally and then builds the Docker
# image and pushes it to this Gitea instance's container registry, tagged with
# the version and `latest`. The tag must match the root package.json version.
#
# Needs a repository (or owner) secret REGISTRY_TOKEN: a Gitea access token
# with package write access for the repository owner. The registry host is
@@ -15,13 +14,16 @@ name: CI
on:
push:
branches: [master]
tags: ['v[0-9]+.[0-9]+.[0-9]+']
pull_request:
env:
REGISTRY: git.hq.ars9.space
jobs:
# Not needed on tag pushes: server and client always run there
changes:
if: ${{ !startsWith(github.ref, 'refs/tags/') }}
runs-on: ubuntu-latest
outputs:
server: ${{ steps.filter.outputs.server }}
@@ -45,7 +47,10 @@ jobs:
server:
needs: changes
if: needs.changes.outputs.server == 'true'
# changes is skipped on tag pushes, hence !cancelled()
if: |
!cancelled() &&
(startsWith(github.ref, 'refs/tags/') || needs.changes.outputs.server == 'true')
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
@@ -65,7 +70,10 @@ jobs:
client:
needs: changes
if: needs.changes.outputs.client == 'true'
# changes is skipped on tag pushes, hence !cancelled()
if: |
!cancelled() &&
(startsWith(github.ref, 'refs/tags/') || needs.changes.outputs.client == 'true')
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
@@ -83,46 +91,20 @@ jobs:
- name: Storybook tests
run: npm run -w client test:storybook
# Skips the image job if the registry already has this version's image
version:
if: github.event_name == 'push'
image:
needs: [server, client]
if: ${{ !failure() && !cancelled() && startsWith(github.ref, 'refs/tags/') }}
runs-on: ubuntu-latest
outputs:
version: ${{ steps.check.outputs.version }}
changed: ${{ steps.check.outputs.changed }}
steps:
- uses: actions/checkout@v4
- id: check
env:
REGISTRY_TOKEN: ${{ secrets.REGISTRY_TOKEN }}
OWNER: ${{ github.repository_owner }}
- name: Check the tag matches package.json
run: |
version=$(node -p "require('./package.json').version")
image="${REGISTRY}/$(echo "${GITHUB_REPOSITORY}" | tr '[:upper:]' '[:lower:]')"
echo "$REGISTRY_TOKEN" | docker login "$REGISTRY" -u "$OWNER" --password-stdin
if docker manifest inspect "${image}:${version}" >/dev/null 2>&1; then
echo "version ${version}: image already in registry, skipping"
echo "changed=false" >> "$GITHUB_OUTPUT"
else
echo "version ${version}: not in registry, building"
echo "changed=true" >> "$GITHUB_OUTPUT"
if [ "${GITHUB_REF_NAME}" != "v${version}" ]; then
echo "tag ${GITHUB_REF_NAME} does not match package.json version ${version}"
exit 1
fi
echo "version=${version}" >> "$GITHUB_OUTPUT"
image:
needs: [server, client, version]
# server/client may be skipped when their paths didn't change
if: |
!failure() && !cancelled() &&
github.event_name == 'push' &&
needs.version.outputs.changed == 'true' &&
(needs.server.result == 'success' || needs.server.result == 'skipped') &&
(needs.client.result == 'success' || needs.client.result == 'skipped')
runs-on: ubuntu-latest
env:
VERSION: ${{ needs.version.outputs.version }}
steps:
- uses: actions/checkout@v4
echo "VERSION=${version}" >> "$GITHUB_ENV"
- name: Log in to the registry
env:
REGISTRY_TOKEN: ${{ secrets.REGISTRY_TOKEN }}
+12
View File
@@ -2,6 +2,18 @@
All notable changes to this project will be documented in this file.
## 1.24.3 - 2026-10-02
Changes since 1.24.2:
### Added
- `examples/` directory with ready-to-import example resources. The first one, `examples/self-test`, is a scenario that tests the liqa instance it runs on: it creates a temporary scenario through the REST API, runs it, checks the run and its page in the UI, and cleans up. It uses an environment, a credential, snippets and assertions.
### Changed
- CI builds and pushes the Docker image only when a `vX.Y.Z` release tag is pushed, not on every merge to `master`.
## 1.24.2 - 2026-10-02
Changes since 1.24.1:
+14 -10
View File
@@ -14,6 +14,7 @@ It is an npm workspace with two packages:
- [docs/development.md](docs/development.md) - local setup, running, testing, Docker
- [docs/scenario.md](docs/scenario.md) - scenario execution, script `context` API, versioning, export/import, Playwright traces
- [docs/mcp.md](docs/mcp.md) - MCP tool reference
- [examples/](examples/README.md) - ready-to-import example resources (YAML); `server/test/examples.spec.ts` imports each file, so keep them in sync with the import format
- [CHANGELOG.md](CHANGELOG.md) - release notes per version
- [Dockerfile](Dockerfile) - single image: builds client and server, runtime serves both
- [.env.example](.env.example) - all configuration variables (validated in `server/src/config/app.config.ts`)
@@ -28,7 +29,9 @@ The live database is `data/liqa.db`. The container applies pending migrations be
## Branching
Never commit directly to `master` when implementing a feature, chore or bug fix: create a separate branch for the work first. Only version-bump release commits (see "Committing a new version") are made on `master`.
Never commit directly to `master` when implementing a feature, chore or bug fix: create a separate branch for the work first, forked from `master`. These commits don't change the version or `CHANGELOG.md`; the branch is merged back to `master` through a pull request. Only release commits (see "Releasing a new version") are made on `master`.
When committing on a work branch, also update the docs affected by the change (`docs/*.md`, `README.md`, `.env.example`, MCP tool descriptions) in the same branch.
## Code quality
@@ -47,17 +50,18 @@ cd client && npm run lint && npm run build && npm run test:storybook
- Server tests use an in-memory DB, a Playwright mock (`server/test/__mocks__/playwright.ts`), and a temporary files directory per test app (see `server/test/app.harness.ts`).
- Import Node.js built-in modules with the `node:` prefix (`node:fs`, `node:path`, `node:crypto`, ...).
## Committing a new version
## Releasing a new version
When asked to commit:
A release is cut on `master` after one or more work branches have been merged (their pull request checks are already green). CI builds and pushes the Docker image only when a `vX.Y.Z` tag is pushed, not on merges.
1. **Ask which version to bump** - major, minor or patch - and propose a sensible default based on the changes: patch for fixes and small behavior/default tweaks, minor for new features, major for breaking changes (e.g. changed API or export/import formats that old clients or files can't use).
2. Run the code quality checks above.
When asked to release:
1. Make sure you're on an up-to-date, clean `master` (`git switch master && git pull`), and collect the changes since the last release: `git log --oneline "$(git describe --tags --abbrev=0)"..HEAD`.
2. **Ask which version to bump** - major, minor or patch - and propose a sensible default based on those changes: patch for fixes and small behavior/default tweaks, minor for new features, major for breaking changes (e.g. changed API or export/import formats that old clients or files can't use).
3. Bump `version` in the root `package.json` and in both places at the top of `package-lock.json` (the root entry and `packages[""]`). `server/package.json` and `client/package.json` keep their own versions; don't bump them.
4. Add a `## <version> - <YYYY-MM-DD>` entry at the top of `CHANGELOG.md` ("Changes since <previous version>:", then `### Added` / `### Changed` / `### Fixed`). Mark breaking changes with **Breaking:**.
5. Update the docs affected by the change (`docs/*.md`, `README.md`, `.env.example`, MCP tool descriptions).
6. Build the commit message with the `/git-commit` skill if it is available, following its format and rules. Otherwise use a conventional commit message (`type(scope): subject`, then a bullet list body). Either way, put the version bump in the body as a bullet (e.g. `- bump version to <version>`), not in the subject line. This overrides the skill's rule of putting versions in the subject. Then make the commit with that message.
7. **Tag the version commit** with an annotated tag `v<version>` whose message is that version's `CHANGELOG.md` entry, verbatim (from its `## <version>` heading up to the next version's heading). Commits without a version bump get no tag. `--cleanup=whitespace` is required: the default cleanup strips lines starting with `#`, which would drop the entry's headings:
5. Commit only these release changes on `master`. Build the commit message with the `/git-commit` skill if it is available, following its format and rules. Otherwise use a conventional commit message (`type(scope): subject`, then a bullet list body). Either way, put the version bump in the body as a bullet (e.g. `- bump version to <version>`), not in the subject line. This overrides the skill's rule of putting versions in the subject.
6. **Tag the release commit** with an annotated tag `v<version>` whose message is that version's `CHANGELOG.md` entry, verbatim (from its `## <version>` heading up to the next version's heading). `--cleanup=whitespace` is required: the default cleanup strips lines starting with `#`, which would drop the entry's headings:
```bash
v=<version>
@@ -65,5 +69,5 @@ When asked to commit:
| git tag -a "v$v" --cleanup=whitespace -F -
```
Don't push the tag; tell the user to push with `git push --follow-tags`, which also pushes annotated tags.
8. **After committing, ask the user whether to rebuild and restart the docker compose containers** (`docker compose up -d --build`); don't do it without confirmation.
7. **Ask the user before pushing**, then push the commit and the tag together with `git push --follow-tags` (it also pushes annotated tags). The tag push triggers the image build; it fails if the tag doesn't match the `package.json` version.
8. **Ask the user whether to rebuild and restart the docker compose containers** (`docker compose up -d --build`); don't do it without confirmation.
+3
View File
@@ -14,6 +14,8 @@ No configuration is needed: every setting has a default. To override one, copy `
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](examples/self-test/): a scenario that tests liqa itself using an environment, a credential and snippets.
---
## Installation
@@ -49,6 +51,7 @@ Scenarios, snippets, environments and credentials can be exported as YAML and im
- [docs/scenario.md](docs/scenario.md) - runs, the script `context` API, versioning, import/export, Playwright traces
- [docs/mcp.md](docs/mcp.md) - MCP tool reference
- [docs/development.md](docs/development.md) - setup, configuration, running, testing, linting, Docker
- [examples/](examples/) - ready-to-import example scenarios
- [CHANGELOG.md](CHANGELOG.md) - release notes
---
+5 -6
View File
@@ -245,13 +245,12 @@ Before adding a dependency, check its license is compatible with MIT distributio
## CI (Gitea Actions)
`.gitea/workflows/ci.yml` runs on pushes to `master` and on pull requests:
`.gitea/workflows/ci.yml` runs on pushes to `master`, on pull requests and on release tags (`vX.Y.Z`):
- **changes**: detects which of `server/` and `client/` changed (via `dorny/paths-filter`), also treating root `package.json`/`package-lock.json` and the workflow file itself as affecting both.
- **server** (skipped if nothing under `server/` changed): lint (no warnings allowed), type-check, tests, build.
- **client** (skipped if nothing under `client/` changed): lint (no warnings allowed), build, Storybook tests in headless Chromium.
- **version** (pushes to `master` only): reads `version` from the root `package.json` and checks the registry for an existing `<registry>/<owner>/<repo>:<version>` image; skips the image job if that tag is already present.
- **image** (pushes to `master` only): when the version job found no existing image for the current version, and the server/client jobs passed or were skipped, builds the Docker image and pushes it to the Gitea container registry set by `REGISTRY` at the top of the workflow (`git.hq.ars9.space`) as `<registry>/<owner>/<repo>:<version>` and `:latest`.
- **changes** (not on tags): detects which of `server/` and `client/` changed (via `dorny/paths-filter`), also treating root `package.json`/`package-lock.json` and the workflow file itself as affecting both.
- **server** (skipped if nothing under `server/` changed; always runs on tags): lint (no warnings allowed), type-check, tests, build.
- **client** (skipped if nothing under `client/` changed; always runs on tags): lint (no warnings allowed), build, Storybook tests in headless Chromium.
- **image** (release tags only): after the server and client jobs pass, checks that the tag matches the root `package.json` version (`v<version>`), builds the Docker image and pushes it to the Gitea container registry set by `REGISTRY` at the top of the workflow (`git.hq.ars9.space`) as `<registry>/<owner>/<repo>:<version>` and `:latest`. Merges to `master` don't build images.
The image job logs in as the repository owner with the `REGISTRY_TOKEN` secret: a Gitea access token with package write access (Settings → Applications → token with `write:package`), added under the repository's Settings → Actions → Secrets. It runs `docker` on the runner, so the runner must give jobs access to a Docker daemon (act_runner mounts the host's Docker socket into job containers by default).
+2
View File
@@ -155,3 +155,5 @@ Run-step status:
5. Assign credentials to scenario aliases when needed
6. Run scenario
7. Wait for run completion and inspect run logs/outputs
The [self-test example](../examples/self-test/) follows these steps through the REST API, and can be imported as a complete, working scenario.
+9
View File
@@ -0,0 +1,9 @@
# Examples
Ready-to-import liqa resources. Each example is a directory with a YAML file to import (the Import page in the UI, `POST /api/v1/import`, or the `import_yaml` MCP tool; see [Import](../docs/scenario.md#import)) and a README on how to run it.
| Example | What it shows |
|---|---|
| [self-test](self-test/) | A scenario that tests the liqa instance it runs on: creates a scenario through the REST API, runs it, checks the run and its page in the UI, and cleans up. Uses an environment, a credential, snippets and assertions |
`server/test/examples.spec.ts` imports every YAML file in this directory and checks that its code parses, so the examples keep up with the import format.
+55
View File
@@ -0,0 +1,55 @@
# Self-test
A scenario that tests the liqa instance it runs on. It drives liqa through its own REST API and web UI: it creates a small scenario, runs it, checks the result and deletes it again. It shows the main liqa features in one place:
- an **environment** with the URLs and test values the steps read with `context.getEnv()`
- a **credential**, assigned to the scenario as `fixture` and read with `context.getCredential()`
- three **snippets**, called with `context.runSnippet()`, one of them from the other two
- **assertions** (`context.assert()` and Playwright's `expect`), step outputs (`context.getStepOutput()`) and run logs
Everything is in [self-test.yaml](self-test.yaml).
## Run it
1. Start liqa with the default docker compose deployment (`docker compose up -d --build` at the repo root). It's served at http://localhost:13000.
2. Import [self-test.yaml](self-test.yaml): open **Import** in the UI and pick the file, or run
```bash
curl -X POST http://localhost:13000/api/v1/import \
-H 'Content-Type: application/yaml' \
--data-binary @examples/self-test/self-test.yaml
```
Every item has a fixed id, so importing the file again updates the same resources instead of adding copies.
3. Open the **liqa self-test** scenario and click **Run**. Its default environment, `liqa-self-test`, is preselected.
The run takes a few seconds. The run page shows every assertion as a log entry, and the target scenario's run while it exists.
## What's in the file
| Kind | Name | Purpose |
|---|---|---|
| Environment | `liqa-self-test` | `liqa_url` (REST API base), `ui_url` (web UI base), `temp_prefix` (name prefix of the temporary resources), `greeting` (test value) |
| Credential | `liqa-self-test-fixture` | Test data (`username`, `token`) that the self-test passes on to the scenario it creates. It's not a real secret |
| Snippet | `liqa-api` | `runSnippet("liqa-api", method, path, body?)`: calls `liqa_url` + `/api/v1` + `path`, returns the parsed JSON and throws on an error status |
| Snippet | `liqa-run-and-wait` | `runSnippet("liqa-run-and-wait", scenarioId, environmentId)`: starts a run and returns it once it has finished. Uses `liqa-api` |
| Snippet | `self-test-cleanup` | Deletes every scenario, credential and environment whose name starts with `temp_prefix` and returns how many it deleted. Uses `liqa-api` |
| Scenario | `liqa self-test` | The self-test itself (below) |
The scenario's steps:
1. **Check the instance is up**: checks `GET /health`, then runs `self-test-cleanup` to remove anything a failed earlier run left behind (and logs a warning if it found some).
2. **Create the target scenario**: creates a temporary environment, a temporary credential (holding the `fixture` credential's data) and the target scenario `[self-test] target scenario`, and assigns the credential to it as `secret`. The target has two steps: one reads `greeting` and the `secret` token, the other renders the greeting on a page and checks it with `expect`.
3. **Run the target scenario**: runs it with `liqa-run-and-wait` and checks the result: the run and both steps passed, the step outputs hold the greeting and the token's length, and the target logged its passing assertion.
4. **Check the run in the UI**: opens the target's run page at `ui_url` and checks that it shows the scenario name and the assertion.
5. **Clean up**: runs `self-test-cleanup` again, and checks that it deleted the three temporary resources and that the target scenario is gone.
## Addresses
Steps run inside the liqa server, so `liqa_url` and `ui_url` are addresses as seen from the server, not from your machine. In the docker compose deployment the server listens on port 3000 inside the container, published as 13000 on the host, so both are `http://localhost:3000`.
When running the server locally (`npm run start:dev`, see [docs/development.md](../../docs/development.md)), `liqa_url` stays `http://localhost:3000`. The UI is then served by the Vite dev server: set `ui_url` to `http://localhost:5173`.
## When it fails
A failed step stops the run, so the temporary resources (named `[self-test] ...`) are left in place to inspect. The next self-test run deletes them in its first step.
+280
View File
@@ -0,0 +1,280 @@
# liqa self-test example: a scenario that tests the liqa instance it runs on.
#
# Import this file (Import page in the UI, POST /api/v1/import with
# Content-Type: application/yaml, or the import_yaml MCP tool), then run the
# "liqa self-test" scenario. See README.md next to this file.
#
# Every item has a fixed id, so importing the file again updates the same
# resources instead of creating duplicates.
---
# Environment: where the liqa under test is reachable from the liqa server
kind: environment
id: 418eacb0-ab16-4ad6-ab50-c0274fdc49f1
name: liqa-self-test
description: >-
The liqa instance the self-test scenario runs against. Steps run inside the
liqa server (the Docker container), so the compose deployment published at
http://localhost:13000 is reached at its in-container port 3000.
data:
# REST API base (without /api/v1)
liqa_url: http://localhost:3000
# Web UI base; use http://localhost:5173 with the Vite dev server
ui_url: http://localhost:3000
# Name prefix of the temporary resources the self-test creates and deletes
temp_prefix: "[self-test] "
# Value the target scenario reads from its own (temporary) environment
greeting: Hello from the liqa self-test
---
# Credential: test data handed over to the temporary target scenario
kind: credential
id: b0c9ccab-6743-4ac1-9017-d99e0f5d7474
name: liqa-self-test-fixture
data: '{"username":"self-test-user","token":"not-a-real-secret-0123456789"}'
---
# Snippet: liqa-api
kind: snippet
id: f9d2612c-266c-411a-9483-5d860599f208
version: 1
alias: liqa-api
title: Call the liqa REST API
description: >-
`context.runSnippet("liqa-api", method, path, body?)` sends a request to
`liqa_url` + `/api/v1` + path and returns the parsed JSON response (`null`
for an empty body). Throws on a non-2xx status.
code: |
const [method, path, body] = args;
const url = context.getEnv("liqa_url") + "/api/v1" + path;
const response = await context.page.request.fetch(url, {
method,
data: body,
// POST /scenarios/:id/run/:runId/wait blocks until the run finishes
timeout: 120_000,
failOnStatusCode: false,
});
const text = await response.text();
if (!response.ok()) {
throw new Error(`${method} ${path} returned ${response.status()}: ${text}`);
}
return text ? JSON.parse(text) : null;
---
# Snippet: liqa-run-and-wait
kind: snippet
id: b36c1075-2700-421f-a2e7-ab1a80adb7e7
version: 1
alias: liqa-run-and-wait
title: Run a scenario and wait for it
description: >-
`context.runSnippet("liqa-run-and-wait", scenarioId, environmentId)` starts
a run of the scenario's latest version and returns the finished run (with
its step runs and logs). Uses the liqa-api snippet.
code: |
const [scenarioId, environmentId] = args;
const run = await context.runSnippet(
"liqa-api",
"POST",
`/scenarios/${scenarioId}/run`,
{ environmentId },
);
context.log(`Started run ${run.id}, waiting for it to finish`);
return context.runSnippet(
"liqa-api",
"POST",
`/scenarios/${scenarioId}/run/${run.id}/wait`,
);
---
# Snippet: self-test-cleanup
kind: snippet
id: f99e3b17-d28d-4a80-8ae4-f7e8252e0be5
version: 1
alias: self-test-cleanup
title: Delete temporary self-test resources
description: >-
Deletes every scenario, credential and environment whose name starts with
the `temp_prefix` environment value, and returns how many were deleted.
Uses the liqa-api snippet.
code: |
const prefix = context.getEnv("temp_prefix");
let deleted = 0;
// Scenarios first: they reference the credentials and environments
for (const path of ["/scenarios", "/credentials", "/environments"]) {
const page = await context.runSnippet("liqa-api", "GET", `${path}?limit=1000`);
for (const item of page.data.filter((i) => i.name.startsWith(prefix))) {
await context.runSnippet("liqa-api", "DELETE", `${path}/${item.id}`);
context.log(`Deleted ${path.slice(1, -1)} "${item.name}"`);
deleted += 1;
}
}
return deleted;
---
# Scenario: liqa self-test
kind: scenario
id: 571b2894-dacc-4428-b459-4e3fefac5908
version: 1
name: liqa self-test
description: |
Tests the liqa instance it runs on, through its REST API and web UI:
1. checks that the instance is up and removes leftovers of earlier runs
2. creates a temporary environment, credential and two-step target scenario
3. runs the target scenario, waits for it and checks its step outputs and logs
4. opens the finished run in the web UI
5. deletes the temporary resources
Uses the `liqa-api`, `liqa-run-and-wait` and `self-test-cleanup` snippets and
the `fixture` credential. See `examples/self-test/README.md`.
environmentId: 418eacb0-ab16-4ad6-ab50-c0274fdc49f1
timeoutSeconds: 300
credentials:
- credentialId: b0c9ccab-6743-4ac1-9017-d99e0f5d7474
alias: fixture
steps:
- title: Check the instance is up
execCode: |
const response = await context.page.request.get(
context.getEnv("liqa_url") + "/health",
);
const health = await response.json();
context.assert(() => response.ok(), "Health endpoint responds", {
status: response.status(),
});
context.assert(() => health.status === "ok", "Health status is ok", health);
// A failed earlier run may have left its temporary resources behind
const deleted = await context.runSnippet("self-test-cleanup");
if (deleted > 0) {
context.warn(`Deleted ${deleted} leftover resource(s) of an earlier run`);
}
return health;
- title: Create the target scenario
execCode: |
const prefix = context.getEnv("temp_prefix");
const api = (method, path, body) =>
context.runSnippet("liqa-api", method, path, body);
const environment = await api("POST", "/environments", {
name: `${prefix}environment`,
data: { greeting: context.getEnv("greeting") },
});
// Hand the fixture credential over to the target scenario
const fixture = context.getCredential("fixture");
const credential = await api("POST", "/credentials", {
name: `${prefix}credential`,
data: JSON.stringify(fixture),
});
const scenario = await api("POST", "/scenarios", {
name: `${prefix}target scenario`,
description: "Temporary scenario created by the liqa self-test",
environmentId: environment.id,
timeoutSeconds: 60,
});
await api("POST", `/scenarios/${scenario.id}/credentials`, {
credentialId: credential.id,
alias: "secret",
});
await api("POST", `/scenarios/${scenario.id}/steps`, {
title: "Read the environment and credential",
execCode: `
const secret = context.getCredential("secret");
context.assert(() => typeof secret.token === "string", "Credential has a token");
// Return the token length, not the token: step outputs are not secret
return { greeting: context.getEnv("greeting"), tokenLength: secret.token.length };
`,
});
await api("POST", `/scenarios/${scenario.id}/steps`, {
title: "Render the greeting",
execCode: `
const { greeting } = await context.getStepOutput(-1);
await context.page.setContent("<h1>" + greeting + "</h1>");
await expect(context.page.locator("h1")).toHaveText(greeting);
return { heading: await context.page.locator("h1").textContent() };
`,
});
const created = await api("GET", `/scenarios/${scenario.id}`);
context.assert(
() => created.steps.length === 2,
"Target scenario has 2 steps",
{ steps: created.steps.length },
);
context.log(`Created target scenario ${scenario.id}`);
return {
scenarioId: scenario.id,
scenarioName: scenario.name,
environmentId: environment.id,
credentialId: credential.id,
};
- title: Run the target scenario
timeoutSeconds: 150
execCode: |
const { scenarioId, environmentId } = await context.getStepOutput(-1);
const run = await context.runSnippet(
"liqa-run-and-wait",
scenarioId,
environmentId,
);
context.assert(() => run.status === "pass", "Target run passed", {
status: run.status,
errors: run.logs.filter((l) => l.level === "error").map((l) => l.message),
});
context.assert(
() => run.stepRuns.every((s) => s.status === "pass"),
"All target steps passed",
run.stepRuns.map((s) => ({ order: s.order, status: s.status })),
);
const [read, render] = run.stepRuns.map((s) => JSON.parse(s.output));
const greeting = context.getEnv("greeting");
context.assert(
() => read.greeting === greeting,
"Target read the greeting from its environment",
read,
);
context.assert(
() => read.tokenLength === context.getCredential("fixture").token.length,
"Target read the token from its credential",
);
context.assert(
() => render.heading === greeting,
"Target rendered the greeting",
render,
);
context.assert(
() =>
run.logs.some(
(l) =>
l.context === "assertion:pass" &&
l.message === "Credential has a token",
),
"Target logged its passed assertion",
);
return { runId: run.id };
- title: Check the run in the UI
execCode: |
const { scenarioId, scenarioName } = await context.getStepOutput(2);
const { runId } = await context.getStepOutput(3);
const page = context.page;
await page.goto(
`${context.getEnv("ui_url")}/scenarios/${scenarioId}/runs/${runId}`,
);
await expect(page.getByText(scenarioName).first()).toBeVisible();
await expect(page.getByText("Credential has a token").first()).toBeVisible();
context.log(`Run page checked: ${page.url()}`);
return { url: page.url() };
- title: Clean up
execCode: |
const { scenarioId } = await context.getStepOutput(2);
const deleted = await context.runSnippet("self-test-cleanup");
context.assert(() => deleted === 3, "Deleted the 3 temporary resources", {
deleted,
});
const response = await context.page.request.get(
`${context.getEnv("liqa_url")}/api/v1/scenarios/${scenarioId}`,
);
context.assert(
() => response.status() === 404,
"Target scenario is gone",
{ status: response.status() },
);
return { deleted };
+2 -2
View File
@@ -1,12 +1,12 @@
{
"name": "liqa",
"version": "1.24.2",
"version": "1.24.3",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "liqa",
"version": "1.24.2",
"version": "1.24.3",
"license": "MIT",
"workspaces": [
"server",
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "liqa",
"version": "1.24.2",
"version": "1.24.3",
"private": true,
"license": "MIT",
"author": "Andrii Arsenin",
+83
View File
@@ -0,0 +1,83 @@
/**
* Keeps the files in `examples/` importable: every YAML file there must pass
* `POST /import`, and all its step and snippet code must parse.
*/
import * as fs from "node:fs";
import * as path from "node:path";
import { INestApplication } from "@nestjs/common";
import request from "supertest";
import { buildTestApp } from "./app.harness";
import { ImportService } from "../src/import/import.service";
const EXAMPLES_DIR = path.resolve(__dirname, "../../examples");
function findYamlFiles(dir: string): string[] {
return fs.readdirSync(dir, { withFileTypes: true }).flatMap((entry) => {
const full = path.join(dir, entry.name);
if (entry.isDirectory()) return findYamlFiles(full);
return /\.ya?ml$/.test(entry.name) ? [full] : [];
});
}
const AsyncFunction = Object.getPrototypeOf(async () => {})
.constructor as new (...args: string[]) => unknown;
interface ExampleItem {
kind: string;
code?: string;
steps?: { title?: string; execCode?: string }[];
}
describe("Examples", () => {
let app: INestApplication;
let importService: ImportService;
beforeAll(async () => {
app = await buildTestApp();
importService = app.get(ImportService);
});
afterAll(async () => {
await app.close();
});
const files = findYamlFiles(EXAMPLES_DIR);
it("has example files", () => {
expect(files.length).toBeGreaterThan(0);
});
describe.each(files.map((f) => [path.relative(EXAMPLES_DIR, f), f]))(
"%s",
(_name, file) => {
const yaml = fs.readFileSync(file, "utf8");
it("imports", async () => {
const res = await request(app.getHttpServer())
.post("/import")
.set("Content-Type", "application/yaml")
.send(yaml)
.expect(201);
expect(res.body.imported.length).toBeGreaterThan(0);
});
it("has code that parses", () => {
const items = importService.parseYaml(yaml) as ExampleItem[];
for (const item of items) {
// Same shape as the executor: snippets get `...args`
if (item.code != null) {
expect(
() => new AsyncFunction("context", "...args", item.code!),
).not.toThrow();
}
for (const step of item.steps ?? []) {
if (step.execCode == null) continue;
expect(
() => new AsyncFunction("context", step.execCode!),
).not.toThrow();
}
}
});
},
);
});