Recent changes to CI CD Integration

CI CD Integration modified by Viktor Fási

Viktor Fási — Wed, 06 May 2026 09:06:53 -0000

--- v2
+++ v3
@@ -1,6 +1,10 @@
 # CI/CD Integration

 Lastest integrates with CI/CD pipelines via the CLI runner and a reusable GitHub Action.
+
+![Development & Review Flow](images/development-flow.png)
+
+End-to-end view: code push → PR → CI/CD pipeline → preview env or staging → Lastest visual validation → manager review → approve & merge or request changes.

 ---

CI CD Integration modified by Viktor Fási

Viktor Fási — Wed, 06 May 2026 09:06:51 -0000

--- v1
+++ v2
@@ -1,6 +1,6 @@
 # CI/CD Integration

-Lastest2 integrates with CI/CD pipelines via the CLI runner and a reusable GitHub Action.
+Lastest integrates with CI/CD pipelines via the CLI runner and a reusable GitHub Action.

 ---

@@ -35,11 +35,11 @@

 ## GitHub Action (Reusable)

-Zero-config CI/CD integration. No local Playwright install needed -- tests run on your Lastest2 server via a remote runner.
+Zero-config CI/CD integration. No local Playwright install needed -- tests run on your Lastest server via a remote runner.

     :::yaml

     - name: Run visual regression tests
-      uses: dexilion-team/lastest2/action@main
+      uses: las-team/lastest/action@main
       with:
         server-url: ${{ secrets.LASTEST_SERVER_URL }}
         runner-token: ${{ secrets.LASTEST_RUNNER_TOKEN }}
@@ -50,7 +50,7 @@

 | Input | Description | Required | Default |
 |-------|-------------|----------|---------|
-| `server-url` | Lastest2 server URL | Yes | - |
+| `server-url` | Lastest server URL | Yes | - |
 | `runner-token` | Runner authentication token | Yes | - |
 | `timeout` | Build completion timeout (seconds) | No | `300` |
 | `fail-on-changes` | Fail when visual changes detected | No | `false` |
@@ -60,7 +60,7 @@
 | Output | Description |
 |--------|-------------|
 | `status` | Build status (`passed`, `failed`, `review_required`, `safe_to_merge`, `blocked`) |
-| `build-url` | Link to build results in Lastest2 |
+| `build-url` | Link to build results in Lastest |
 | `changed-count` | Number of visual changes detected |
 | `passed-count` | Number of passed tests |
 | `failed-count` | Number of failed tests |
@@ -70,7 +70,7 @@

 ### Setup

-1. Register a remote runner in Lastest2 (Settings > Runners)
+1. Register a remote runner in Lastest (Settings > Runners)

 2. Copy the runner token
 3. Add `LASTEST_SERVER_URL` and `LASTEST_RUNNER_TOKEN` as GitHub repository secrets
 4. Add the action to your workflow
@@ -83,7 +83,7 @@


 1. Requires a GitHub or GitLab connection
 2. Select a feature branch (not main/master)
-3. Lastest2 compares against the default branch via the API
+3. Lastest compares against the default branch via the API
 4. Tests are matched to changed files by URL patterns and code references
 5. Only affected tests run

CI CD Integration modified by Viktor Fási

Viktor Fási — Wed, 06 May 2026 09:06:48 -0000

CI/CD Integration

Lastest2 integrates with CI/CD pipelines via the CLI runner and a reusable GitHub Action.

CLI Test Runner

Run visual regression tests from the command line:

pnpm test:visual --repo-id <id> [options]

Options

Flag	Description	Default
`--repo-id <id>`	Repository ID (required)	-
`--base-url <url>`	Override target URL	`http://localhost:3000`
`--headless`	Run in headless mode	`true`
`--no-headless`	Run with visible browser	-
`--output-dir <dir>`	Screenshot output directory	`./test-output`

Example: GitHub Actions with CLI

- name: Run Visual Tests
  run: pnpm test:visual --repo-id ${{ env.REPO_ID }} --base-url http://localhost:3000
  env:
    REPO_ID: your-repo-id

The runner automatically captures GITHUB_HEAD_REF, GITHUB_REF_NAME, and GITHUB_SHA for git tracking.

GitHub Action (Reusable)

Zero-config CI/CD integration. No local Playwright install needed -- tests run on your Lastest2 server via a remote runner.

- name: Run visual regression tests
  uses: dexilion-team/lastest2/action@main
  with:
    server-url: ${{ secrets.LASTEST_SERVER_URL }}
    runner-token: ${{ secrets.LASTEST_RUNNER_TOKEN }}
    timeout: '300'
    fail-on-changes: 'false'

Inputs

Input	Description	Required	Default
`server-url`	Lastest2 server URL	Yes	-
`runner-token`	Runner authentication token	Yes	-
`timeout`	Build completion timeout (seconds)	No	`300`
`fail-on-changes`	Fail when visual changes detected	No	`false`

Outputs

Output	Description
`status`	Build status (`passed`, `failed`, `review_required`, `safe_to_merge`, `blocked`)
`build-url`	Link to build results in Lastest2
`changed-count`	Number of visual changes detected
`passed-count`	Number of passed tests
`failed-count`	Number of failed tests
`total-tests`	Total number of tests run

Results are automatically posted to the GitHub Actions step summary.

Setup

Register a remote runner in Lastest2 (Settings > Runners)
Copy the runner token
Add LASTEST_SERVER_URL and LASTEST_RUNNER_TOKEN as GitHub repository secrets
Add the action to your workflow

Smart Run

Run only tests affected by your code changes:

Requires a GitHub or GitLab connection
Select a feature branch (not main/master)
Lastest2 compares against the default branch via the API
Tests are matched to changed files by URL patterns and code references
Only affected tests run

This dramatically reduces CI time for large test suites.

Webhook-Triggered Builds

Configure webhooks in GitHub or GitLab to trigger builds automatically:

GitHub

Connect your GitHub account in Settings
Enable webhooks for your repository
Builds trigger on PR open/update/push

GitLab

Connect your GitLab account in Settings
Enable webhooks for your project
Builds trigger on MR open/update/push

Results are posted back as PR/MR comments automatically.