Test workflow (simov/grant)

The Test workflow from simov/grant, 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: simov/grant.github/workflows/test.ymlLicense MITView source

What it does

This is the Test workflow from the simov/grant 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
on:
  push:
    branches:
      - master
  pull_request:
    branches:
      - master
jobs:
  test:
    name: Node.js
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os:
          - ubuntu-latest
        node:
          - 22
          - 20
          - 18
          - 16
          - 14
    steps:
      # -----------------------------------------------------------------------
      - name: Clone default branch
        uses: actions/checkout@v2
        with:
          persist-credentials: false
      # -----------------------------------------------------------------------
      - name: Set Node.js version
        uses: actions/setup-node@v2
        with:
          node-version: ${{ matrix.node }}
      # -----------------------------------------------------------------------
      - name: Cache node_modules
        id: cache-modules
        uses: actions/cache@v3
        with:
          path: node_modules
          key: ${{ matrix.os }}-${{ matrix.node }}-${{ hashFiles('package.json') }}
      # -----------------------------------------------------------------------
      - name: Install deps
        if: steps.cache-modules.outputs.cache-hit != 'true'
        run: |
          npm install
      # -----------------------------------------------------------------------
      - name: Run Tests
        run: |
          npm 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
on:
  push:
    branches:
      - master
  pull_request:
    branches:
      - master
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  test:
    timeout-minutes: 30
    name: Node.js
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os:
          - ubuntu-latest
        node:
          - 22
          - 20
          - 18
          - 16
          - 14
    steps:
      # -----------------------------------------------------------------------
      - name: Clone default branch
        uses: actions/checkout@v2
        with:
          persist-credentials: false
      # -----------------------------------------------------------------------
      - name: Set Node.js version
        uses: actions/setup-node@v2
        with:
          cache: 'npm'
          node-version: ${{ matrix.node }}
      # -----------------------------------------------------------------------
      - name: Cache node_modules
        id: cache-modules
        uses: actions/cache@v3
        with:
          path: node_modules
          key: ${{ matrix.os }}-${{ matrix.node }}-${{ hashFiles('package.json') }}
      # -----------------------------------------------------------------------
      - name: Install deps
        if: steps.cache-modules.outputs.cache-hit != 'true'
        run: |
          npm install
      # -----------------------------------------------------------------------
      - name: Run Tests
        run: |
          npm 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

This workflow runs 1 job (5 with the matrix expanded) 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