Continuous E2E testing on GitHub Actions: run the suite all day at a flat price

Coding agents push code around the clock, and your end-to-end suite is the check that sees what their unit tests don't: whether sign-in, checkout and the pages around a change still work together. A team that runs E2E once a night finds a regression merged in the morning only after the next night's run, with a day of merges on top of it. Running the suite all day fixes that, and on per-minute runners it is the most expensive thing in CI: one 4 vCPU runner busy all month is $500.40 on GitHub.

Skipbox runs the loop for a flat $39 a month with unlimited minutes, on your own machine that keeps the browsers and packages installed between runs. Moving is one line, runs-on: skipbox.

Run it on every push, and on a loop

Two triggers in one workflow:

• On every push to a pull request, so a regression is caught before it merges.
• On a schedule against main or staging, every 15 minutes, so flaky tests, regressions that slipped through, and breakage from outside your code (a payment sandbox, an auth provider, a browser update) show up within minutes.

GitHub's shortest schedule is every 5 minutes, on the default branch's latest commit. A concurrency group keeps the loop from stacking up, and Playwright's retries mark tests that fail and then pass as flaky, so a test that flakes once in fifty runs shows up twice a day instead of hiding for a week.

What the loop costs on per-minute runners

A loop every 15 minutes is 96 runs a day. With a few shards, the runner is busy most of the day, every day:

GitHub's figures are after GitHub Team's included usage. Four shards on the loop means four rows like the last one. Try your own minutes in the calculator on the home page.

That bill is why most teams don't run E2E all day, and they pay for it in hours: a regression an agent merged at night is found in the morning, after more commits landed on it, and bisecting it takes the time the loop would have saved. Agent-started pull requests keep rising (GitHub reported more than 40% in September 2026, up from 17% in March), and a budget that caps the per-minute bill stops the jobs mid-month, which turns the loop off exactly when it is needed.

Running the loop yourself

To keep it on GitHub-hosted runners and affordable, teams end up doing this:

• Thinning the schedule to hourly or nightly and accepting slower detection
• Tuning which tests run on which trigger so the minutes fit the budget
• Sharding to finish faster, then paying each shard's setup again
• Or running their own self-hosted runner for the loop, and keeping its browsers, OS and disk healthy

Skipbox removes the trade-off. The loop costs the same however often it runs, and nobody looks after the machine.

What Skipbox gives the loop

A flat price for all-day runs. Each plan runs its jobs around the clock with unlimited minutes. Skipbox jobs use no GitHub minutes, so a GitHub budget never turns the loop off.

Your plans' vCPU set how many shards run at once: four runs-on: skipbox shards run together on four S plans or one L. Shards past that wait their turn.

Setup that doesn't repeat. Each plan comes with your account's own machine, kept between jobs. Playwright's browsers in ~/.cache/ms-playwright, npm's cache, and the Docker images your app and its services use are on the disk for the next run.

Each run starts clean. The runner's credentials, processes and every container are wiped after each job, and a health check runs. A machine that fails it is rebuilt from a clean image. From 13 November 2026, your checkout and its build output (Cargo's target/) stay on your own machine for your next jobs; Clean every job gives each job a fresh machine.

Moving is one line

name: E2E
on:
  pull_request:
  schedule:
    - cron: "*/15 * * * *"
concurrency:
  group: e2e-${{ github.ref }}
  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
jobs:
  e2e:
    runs-on: skipbox # was ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - uses: actions/setup-node@v6
        with:
          node-version: lts/*
      - run: npm ci
      - run: npx playwright install --with-deps
      - run: npx playwright test

1. Sign in to Skipbox with GitHub.
2. Install the Skipbox GitHub App and pick the repositories.
3. Change runs-on and push.

Security

• The machine is your account's alone. No other company's jobs run on it.
• After every job, the runner's credentials, processes and containers are wiped. From 13 November 2026, your checkout and its build output (Cargo's target/) stay on your own machine for your next jobs; Clean every job gives each job a fresh machine.
• Code from people without write access (such as pull requests from forks) runs on a fresh, throwaway machine.

The details are in how jobs are isolated.

Try it

The trial is free for 7 days or 3,000 job-minutes, whichever comes first, with no card. It runs one runs-on: skipbox job at a time: move the E2E job, turn on the schedule, and watch a day of runs on a flat price.

Updated November 11, 2026