E2E Test workflow (react-hook-form/react-hook-form)

The E2E Test workflow from react-hook-form/react-hook-form, explained and optimized by Latchkey.

What it does

This is the E2E Test workflow from the react-hook-form/react-hook-form 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

name: E2E Test

on: [pull_request]

jobs:
  cypress-run:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v6

      - name: Install Dependencies
        uses: ./.github/actions/install-dependencies

      - name: Cypress run
        uses: cypress-io/github-action@v7
        with:
          start: pnpm start
          wait-on: 'http://ip6-localhost:3000'
          wait-on-timeout: 120

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: E2E Test
 
on: [pull_request]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  cypress-run:
    timeout-minutes: 30
    runs-on: latchkey-small
 
    steps:
      - uses: actions/checkout@v6
 
      - name: Install Dependencies
        uses: ./.github/actions/install-dependencies
 
      - name: Cypress run
        uses: cypress-io/github-action@v7
        with:
          start: pnpm start
          wait-on: 'http://ip6-localhost:3000'
          wait-on-timeout: 120
 

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 uses latchkey-small; pick the runner size that fits the job.
• Cancel superseded runs when a branch or PR gets a newer push.
• 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:

• End-to-end and browser tests

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow