testing

A collection of testing guidance and browser-test tools for a software project. It covers unit tests, manual checks, and headless smoke tests, which run basic checks without opening a visible browser.

In plain words
What is it for?
Use it to install and run the test suite, perform one-off test runs, check browser behavior, and verify HTML, CSS, themes, storage, and interface modules.
Why use it?
It gives developers repeatable commands and test patterns for checking individual modules and the application in a real or simulated browser.

Agent

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.

agentmods
npx agentmods add agents/windviki/vbookmarks/testing
Clone the repo
git clone --depth 1 https://github.com/windviki/vBookmarks
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,893 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.03893
Opus 5 $0.00000 $0.01946
Sonnet 5 $0.00000 $0.00779
Haiku 4.5 $0.00000 $0.00389

Measured 2d ago against content hash 164e948e947d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing 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 2d 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.

docs/agents/testing.md · 42 lines

How it starts

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

Testing & Real-Browser Harness (detail)

Extracted verbatim from AGENTS.md — the detailed halves of "Unit tests", "Manual testing checklist" and "Headless smoke test (Docker)". AGENTS.md keeps the commands and the core rules.

Unit tests (detail)

npm install        # installs vitest + sinon (devDependencies)
npm test           # vitest in watch mode
npm run test:run   # single run

Test files (88 — one per module/feature, plus the CSS/HTML contract suites; the exact count is npm run test:run output; each src/ module row above names its own suite): harness patterns are sandbox-eval (fs + new Function) for classic scripts (tests/store.test.js, tests/sort-utils.test.js, tests/sync-manager-client.test.js, tests/options.test.js — the options-page backup suite, which evaluates the real store.js + options.js against a stub DOM; tests/popup.test.js — the classic-script panel heartbeat/pagehide/pageshow/size-restore suite) and direct ESM import with chrome.*/DOM doubles injected on globalThis for the rest — tests/theme.test.js (design-token and theme-locale contract), tests/scrollbar-contract.test.js (horizontal-scrollbar protection contract: every scrollable pane clips overflow-x, text slots ellipsis, fixed slots flex: none, zoom rules never alter geometry, the sync-tooltip 98e29b3 regression pairing — the real-layout matrix is the Docker verify-scrollbars.js), tests/search-core.test.js, the ten P1 module suites (separators/dialogs/search/actions/context-menu/keyboard/dnd/tree-render/tree-view/sync-ui), the P2/P3 feature suites (palette/palette-commands/dupes/session/undo/dead-links/dead-proxy/dead-scan-sw/risk-banner/sync-engine), and the v4 task-2 view-system suites (view-manager/view-recent/view-dupes/view-dead/visit-stats/view-stats/visit-stats-sw) plus 4.1.0's view-tabgroups and version-bump, plus the 4.0.1 additions (dropdown/version/tab-groups-sw/options-proxy/sort-folder) and tests/focus-regression.test.js — the cross-module focus gate that wires the REAL view-manager + palette + keyboard together so the focus-transfer chains (view-jump keys, dialog/palette ownership, layered Esc) are asserted end-to-end. tests/background.test.js imports the real service worker once against an import-time chrome double (dual callback/promise storage, captured listeners) and drives the onCommand branches + the quick-add context menu. tests/fuzzy.test.js also asserts the pages/popup.html/pages/sidepanel.html script-list parity. Never copy the implementation under test into a test.

Read the full file on GitHub · 42 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. 2d ago First seen · 42 lines · 0 tokens per session scan A 164e948e947d

Subscribe to this mod's changes

testing is an agent published in the GitHub repository windviki/vBookmarks (133 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,893 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-08-30.