testing-electron

testing-electron is a cursor rule for Cursor from adonai-labs/agent-runway. It costs 0 tokens per session (818 once invoked), scanned A, original, MIT.

A set of testing guidelines for Electron desktop apps, covering the main process, renderer interface, inter-process communication, and end-to-end tests.

In plain words
What is it for?
Use it to test Electron windows, lifecycle events, IPC handlers, preload APIs, renderer components, native modules, and end-to-end user journeys.
Why use it?
It helps test desktop-specific behaviour without depending on a real Electron runtime for every check, while still covering communication and full-app flows.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it to test Electron windows, lifecycle events, IPC handlers, preload APIs, renderer components, native modules, and end-to-end user journeys.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/adonai-labs/agent-runway/testing-electron
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/adonai-labs/agent-runway

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for testing-electron

README.md
[![agentmods](https://agentmods.dev/badge/rules/adonai-labs/agent-runway/testing-electron/github.svg)](https://agentmods.dev/rules/adonai-labs/agent-runway/testing-electron)
Your own site
<a href="https://agentmods.dev/rules/adonai-labs/agent-runway/testing-electron"><img src="https://agentmods.dev/badge/rules/adonai-labs/agent-runway/testing-electron/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for testing-electron

Your own site · 80×15
<a href="https://agentmods.dev/rules/adonai-labs/agent-runway/testing-electron"><img src="https://agentmods.dev/badge/rules/adonai-labs/agent-runway/testing-electron.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 818 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00818
Opus 5.5 $0.00000 $0.00327
Sonnet 5.5 $0.00000 $0.00164
Haiku 4.5 $0.00000 $0.00082

Measured 1mo ago against content hash 5e6bdb1d94d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing-electron scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/stacks/electron/testing-electron.mdc · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing Electron Applications

Extends core/rules/testing.mdc with Electron-specific testing patterns.


Main Process Testing

  • Mock Electron APIs (app, BrowserWindow, ipcMain) for unit tests
  • Test window creation, lifecycle, and configuration in isolation
  • Test IPC handler registration and message routing
  • Mock file system operations and native modules
  • Test app lifecycle events (ready, window-all-closed, etc.)

Example:

import { BrowserWindow } from 'electron';

jest.mock('electron', () => ({
  BrowserWindow: jest.fn(),
  app: {
    on: jest.fn(),
    quit: jest.fn(),
  },
}));

Renderer Process Testing

  • Mock window.electronAPI or contextBridge exports
  • Avoid real Electron APIs in unit tests
  • Test components independently of IPC
  • Mock preload script exports
  • Use JSDOM or similar for DOM testing

Example:

// Mock window.electronAPI
global.window.electronAPI = {
  send: jest.fn(),
  on: jest.fn(),
};

IPC Testing

  • Handler validation: Test that IPC handlers validate input types and shapes
  • Return values: Assert handlers return expected data structures
  • Error handling: Test error scenarios and ensure proper error messages
  • Bidirectional: Test both ipcMain.handle and ipcRenderer.invoke paths
  • Security: Verify handlers check permissions before performing sensitive operations

Example:

// Test IPC handler
const result = await ipcMain.handlers.get('get-user')(event, userId);
expect(result).toMatchObject({ id: userId, name: expect.any(String) });

React + Electron Testing

  • Custom hooks: Use @testing-library/react-hooks with renderHook and act
  • Context providers: Wrap components under test with Electron context providers
  • Electron APIs in hooks: Mock Electron APIs before invoking hooks that call them
  • Event listeners: Test cleanup of IPC event listeners on unmount

Example:

import { renderHook } from '@testing-library/react-hooks';

const { result } = renderHook(() => useElectronStore(), {
  wrapper: ElectronProvider,
});

Read the full file on GitHub · 128 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 128 lines · 0 tokens per session scan A 5e6bdb1d94d9

Subscribe to this mod's changes

testing-electron is a cursor rule published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 818 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other cursor rules, from other repositories