Tests workflow (quilljs/quill)
The Tests workflow from quilljs/quill, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get caching, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Tests workflow from the quilljs/quill repository, a real project running GitHub Actions. It is shown here with attribution under its BSD-3-Clause license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
name: Tests
on:
workflow_call:
jobs:
e2e:
name: E2E Tests
timeout-minutes: 60
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: 20
- name: Install dependencies
run: npm ci
- name: Install Playwright Browsers
run: npx playwright install --with-deps
working-directory: packages/quill
- name: Run Playwright tests
uses: coactions/setup-xvfb@v1
with:
run: npm run test:e2e -- --headed
working-directory: packages/quill
fuzz:
name: Fuzz Tests
runs-on: ubuntu-latest
steps:
- name: Git checkout
uses: actions/checkout@v4
- name: Use Node.js
uses: actions/setup-node@v4
with:
node-version: 20
- run: npm ci
env:
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD: 1
- run: npm run test:fuzz -w quill
unit:
name: Unit Tests
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
browser: [chromium, webkit, firefox]
steps:
- name: Git checkout
uses: actions/checkout@v3
- name: Use Node.js
uses: actions/setup-node@v3
with:
node-version: 20
- run: npm ci
- run: npx playwright install --with-deps
- run: npm run lint
- run: npm run test:unit -w quill || npm run test:unit -w quill || npm run test:unit -w quill
env:
BROWSER: ${{ matrix.browser }}
The same workflow, on Latchkey
Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.
name: Tests on: workflow_call: jobs: e2e: name: E2E Tests timeout-minutes: 60 runs-on: latchkey-small steps: - uses: actions/checkout@v3 - uses: actions/setup-node@v3 with: cache: 'npm' node-version: 20 - name: Install dependencies run: npm ci - name: Install Playwright Browsers run: npx playwright install --with-deps working-directory: packages/quill - name: Run Playwright tests uses: coactions/setup-xvfb@v1 with: run: npm run test:e2e -- --headed working-directory: packages/quill fuzz: timeout-minutes: 30 name: Fuzz Tests runs-on: latchkey-small steps: - name: Git checkout uses: actions/checkout@v4 - name: Use Node.js uses: actions/setup-node@v4 with: cache: 'npm' node-version: 20 - run: npm ci env: PUPPETEER_SKIP_CHROMIUM_DOWNLOAD: 1 - run: npm run test:fuzz -w quill unit: timeout-minutes: 30 name: Unit Tests runs-on: latchkey-small strategy: fail-fast: false matrix: browser: [chromium, webkit, firefox] steps: - name: Git checkout uses: actions/checkout@v3 - name: Use Node.js uses: actions/setup-node@v3 with: cache: 'npm' node-version: 20 - run: npm ci - run: npx playwright install --with-deps - run: npm run lint - run: npm run test:unit -w quill || npm run test:unit -w quill || npm run test:unit -w quill env: BROWSER: ${{ matrix.browser }}
What changed
- Run on Latchkey managed runners with one line (
runs-on), which apply the fixes below automatically and self-heal transient failures. This example useslatchkey-small; pick the runner size that fits the job. - Cache dependency installs on the setup step so they are served from cache.
- Add a job timeout so a hung step cannot burn hours of runner time.
1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.
What Latchkey heals here
This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:
- Dependency installs
- End-to-end and browser tests
This workflow runs 3 jobs (5 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.