Unit tests workflow (cdpuk/ha-bestway)
The Unit tests workflow from cdpuk/ha-bestway, explained and optimized by Latchkey.
CI health: C - fair
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 Unit tests workflow from the cdpuk/ha-bestway 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: Unit tests
on:
pull_request:
push:
branches: [main]
schedule:
- cron: "0 0 * * *"
jobs:
test:
runs-on: "ubuntu-latest"
name: Run tests
steps:
- name: Check out code from GitHub
uses: actions/checkout@v4
- name: Setup Python
uses: actions/setup-python@v5
with:
python-version: "3.14"
cache: pip
cache-dependency-path: requirements*.txt
- name: Install requirements
run: python3 -m pip install -r requirements_test.txt
- name: Run tests
run: |
pytest \
-qq \
--timeout=9 \
--durations=10 \
-n auto \
--cov custom_components.bestway \
-o console_output_style=count \
-p no:sugar \
tests
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
--- name: Unit tests on: pull_request: push: branches: [main] schedule: - cron: "0 0 * * *" concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: test: timeout-minutes: 30 runs-on: "ubuntu-latest" name: Run tests steps: - name: Check out code from GitHub uses: actions/checkout@v4 - name: Setup Python uses: actions/setup-python@v5 with: python-version: "3.14" cache: pip cache-dependency-path: requirements*.txt - name: Install requirements run: python3 -m pip install -r requirements_test.txt - name: Run tests run: | pytest \ -qq \ --timeout=9 \ --durations=10 \ -n auto \ --cov custom_components.bestway \ -o console_output_style=count \ -p no:sugar \ tests
What changed
- 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.
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 per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.