ghostkit/.github/workflows/tests-e2e.yml at master · nk-crew/ghostkit · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
name: End-to-End Tests

on:
  pull_request:
  push:
    branches:
      - master
  # Allow manually triggering the workflow.
  workflow_dispatch:

permissions:
  contents: read

# Cancels all previous workflow runs for pull requests that have not completed.
concurrency:
  # The concurrency group contains the workflow name and the branch name for pull requests
  # or the commit hash for any other events.
  group: ${{ github.workflow }}-${{ github.event_name == 'pull_request' && github.head_ref || github.sha }}
  cancel-in-progress: true

jobs:
  playwright:
    name: Playwright
    # 2 vCPU, not 4. `workers: 1` does not make this job single-threaded -- the
    # browser and the wp-env stack use the other cores, and measuring the switch
    # showed `playwright test` getting 40-70% slower. It still wins: Blacksmith
    # bills per vCPU and meters the free tier in 2 vCPU minutes, so halving the
    # rate more than covers the extra wall time. Move back to 4 vCPU if the
    # slower feedback on a pull request stops being worth the saving.
    runs-on: blacksmith-2vcpu-ubuntu-2404
    timeout-minutes: 30
    if: ${{ github.repository == 'nk-crew/ghostkit' || github.event_name == 'pull_request' }}

    steps:
      - uses: actions/checkout@v4

      - name: Setup Node.js and install dependencies
        uses: ./.github/setup-node

      - name: Cache Playwright browsers
        uses: actions/cache@v4
        with:
          path: ~/.cache/ms-playwright
          key: playwright-${{ runner.os }}-${{ hashFiles('package-lock.json') }}
          restore-keys: |
            playwright-${{ runner.os }}-

      - name: Npm build
        run: npm run build

      # Chromium only. The shared preset gates its webkit and firefox projects
      # behind `@webkit` and `@firefox` tags and no spec carries either, so the
      # other two browsers were downloaded on every run and never launched. Tag a
      # spec and add the browser back here if that changes.
      - name: Install Playwright dependencies
        run: |
          npx playwright install --with-deps chromium

      - name: Install WordPress and start the server
        run: |
          npm run wp-env start

      - name: Run the tests
        run: |
          xvfb-run --auto-servernum --server-args="-screen 0 1280x960x24" -- npm run test:e2e

      - name: Archive debug artifacts (screenshots, traces)
        uses: actions/upload-artifact@v4
        if: ${{ failure() && !cancelled() }}
        with:
          name: failures-artifacts${{ matrix.plugin && format('-{0}', matrix.plugin) || '' }}
          path: artifacts/test-results
          if-no-files-found: ignore