Test Suite workflow (GoogleChrome/workbox)

The Test Suite workflow from GoogleChrome/workbox, explained and optimized by Latchkey.

CI health: D - needs work

Run this on Latchkey for self-healing, caching, and up to 58% lower cost.

Grade your own workflow free or run it on Latchkey →

Source: GoogleChrome/workbox.github/workflows/pull-request.ymlLicense MITView source

What it does

This is the Test Suite workflow from the GoogleChrome/workbox repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)

name: Test Suite

on: [pull_request]

jobs:
  Node_Tests_Windows:
    runs-on: windows-latest

    steps:
      - uses: actions/checkout@v6

      - uses: actions/setup-node@v6
        with:
          node-version-file: '.nvmrc'

      - name: Get npm cache directory
        id: npm-cache
        run: |
          echo "::set-output name=dir::$(npm config get cache)"
      - uses: actions/cache@v5
        with:
          path: ${{ steps.npm-cache.outputs.dir }}
          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
          restore-keys: |
            ${{ runner.os }}-node-

      - name: Setup
        run: |
          npm ci
          npx gulp build

      - run: npx gulp test_node

  Full_Suite_Mac:
    runs-on: macos-latest

    steps:
      - uses: actions/checkout@v6

      - uses: actions/setup-node@v6
        with:
          node-version-file: '.nvmrc'

      - uses: actions/cache@v5
        with:
          path: ~/.npm
          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
          restore-keys: |
            ${{ runner.os }}-node-

      - uses: actions/cache@v5
        with:
          path: ~/.selenium-assistant
          key: ${{ runner.os }}-selenium-assistant-${{ github.run_id }}
          restore-keys: |
            ${{ runner.os }}-selenium-assistant-

      - name: Setup
        run: |
          sudo safaridriver --enable
          npm ci
          npx gulp build

      - run: npx gulp test

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: Test Suite
 
on: [pull_request]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  Node_Tests_Windows:
    timeout-minutes: 30
    runs-on: windows-latest
 
    steps:
      - uses: actions/checkout@v6
 
      - uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version-file: '.nvmrc'
 
      - name: Get npm cache directory
        id: npm-cache
        run: |
          echo "::set-output name=dir::$(npm config get cache)"
      - uses: actions/cache@v5
        with:
          path: ${{ steps.npm-cache.outputs.dir }}
          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
          restore-keys: |
            ${{ runner.os }}-node-
 
      - name: Setup
        run: |
          npm ci
          npx gulp build
 
      - run: npx gulp test_node
 
  Full_Suite_Mac:
    timeout-minutes: 30
    runs-on: macos-latest
 
    steps:
      - uses: actions/checkout@v6
 
      - uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version-file: '.nvmrc'
 
      - uses: actions/cache@v5
        with:
          path: ~/.npm
          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
          restore-keys: |
            ${{ runner.os }}-node-
 
      - uses: actions/cache@v5
        with:
          path: ~/.selenium-assistant
          key: ${{ runner.os }}-selenium-assistant-${{ github.run_id }}
          restore-keys: |
            ${{ runner.os }}-selenium-assistant-
 
      - name: Setup
        run: |
          sudo safaridriver --enable
          npm ci
          npx gulp build
 
      - run: npx gulp test

What changed

Cancel superseded runs when a branch or PR gets a newer push.
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.

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 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow

actions/checkout actions/setup-node actions/cache