← Back to all tools

Extract Failing Django Tests — Chrome Extension

Adds two buttons directly on GitHub Actions job pages so you can extract failing tests without leaving the page or copy-pasting logs.

How it works

When you open a GitHub Actions job page (github.com/*/actions/runs/*/job/*), a small toolbar appears in the bottom-right corner:

Copy Failing Tests View Failing Tests

Copy Failing Tests — fetches the raw logs using your existing GitHub session (no token needed), extracts failing test paths, and copies them space-separated to your clipboard in one click.
View Failing Tests — opens a panel showing all extracted tests with the common module prefix dimmed so the unique test names stand out. Includes its own copy button.

Installation

This is an unpacked Chrome extension loaded from a local folder — no Web Store required.

Clone or download the tools repository so you have the extract-failing-test-from-github-logs-chrome-extension/ folder locally.
Open Chrome and go to chrome://extensions in the address bar.
Enable Developer mode using the toggle in the top-right corner.
Click Load unpacked and select the extract-failing-test-from-github-logs-chrome-extension/ folder. Chrome will show a confirmation with the permissions the extension needs — click Add extension to confirm.
The extension is now active. Open any GitHub Actions job page and the toolbar will appear automatically.

After updating the extension files (e.g. pulling new changes), go to chrome://extensions, click the refresh icon on the extension card, then reload the GitHub tab.

Permissions

Chrome will ask you to confirm these when you click Load unpacked:

clipboardWrite Write text to the clipboard when you click copy.
github.com Inject the toolbar on GitHub Actions job pages and fetch raw log files using your existing GitHub session.

No token or login required. The extension piggybacks on your existing GitHub browser session — the same one used when you click "View raw logs" manually.