Test workflow (bytenode/bytenode)
The Test workflow from bytenode/bytenode, 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 →What it does
This is the Test workflow from the bytenode/bytenode 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
# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
name: Test
on:
pull_request:
branches: [master]
push:
branches: [master]
jobs:
build:
strategy:
matrix:
node-version: [22.x, 24.x]
os: [ubuntu-latest]
# run pre-flight tests on ubuntu, instead of full OS support matrix, to reduce costs
runs-on: ${{ matrix.os }}
steps:
- uses: actions/checkout@v4
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node-version }}
- uses: actions/cache@v4
with:
path: ~/.npm
key: npm-${{ runner.os }}-${{ matrix.node-version }}-${{ hashFiles('**/package.json') }}
restore-keys: |
npm-${{ runner.os }}-${{ matrix.node-version }}-
- name: Install Packages
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.
# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node # For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions name: Test on: pull_request: branches: [master] push: branches: [master] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: build: timeout-minutes: 30 strategy: matrix: node-version: [22.x, 24.x] os: [ubuntu-latest] # run pre-flight tests on ubuntu, instead of full OS support matrix, to reduce costs runs-on: ${{ matrix.os }} steps: - uses: actions/checkout@v4 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@v4 with: cache: 'npm' node-version: ${{ matrix.node-version }} - uses: actions/cache@v4 with: path: ~/.npm key: npm-${{ runner.os }}-${{ matrix.node-version }}-${{ hashFiles('**/package.json') }} restore-keys: | npm-${{ runner.os }}-${{ matrix.node-version }}- - name: Install Packages 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 (2 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.