Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

vitest-dom

Estrelas11

Forks0

Atualizado16 de julho de 2026 às 09:51

Use vitest + jsdom for fast, lightweight unit tests for front-end apps

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

sanand0

sanand0/scripts

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	vitest-dom
description	Use vitest + jsdom for fast, lightweight unit tests for front-end apps

Use vitest and jsdom for front-end testing.
Avoid vitest.config.*; default ESM import works, launch via "test": "npx -y vitest run" in package.json. Add jsdom as a devDependency. Add npm test to prepublishOnly
Treat tests as lightweight integration, not unit. Load the full HTML + scripts and verify real DOM mutations; ensures refactors don't silently break UI wiring.
Log browser console.* output.
Mount local HTML. settings.fetch.virtualServers = [{url:"https://test/", directory: <root>}]. Use page.goto("https://test/...") to load files without a dev-server.
Create a fresh page for each test to isolate window, document, etc.
Fake timers for deterministic testing.
- Call vi.useFakeTimers() in beforeAll, vi.useRealTimers() in afterAll.
- Re-bind window.setTimeout = setTimeout so app code sees the mocked clock.
- Drive async paths with vi.advanceTimersByTime(ms) instead of await sleep.
Stub external APIs with vi.fn() - e.g. window.fetch = vi.fn(() => Promise.resolve({ok:true,...})) avoids network and lets you assert payloads.
Spy on side-effects - vi.spyOn(console, "error"), clipboard reads, etc.; always mockRestore() afterwards to prevent bleed-through.
Add timeouts per test case, e.g. { timeout: 10_000 }, for long-running tests.

Mais deste repositório

mesmo repositório

code

sanand0/scripts

ALWAYS follow this style when writing Python / JavaScript code

2026-07-2511

data-viz

sanand0/scripts

To select, design, annotate, and verify a data visualization (chart, map, or table).

2026-07-2511

design

sanand0/scripts

ALWAYS follow this design guide for any front-end work

2026-07-2511

expert-lens

sanand0/scripts

Use this for non-trivial analysis, design, diagnosis, review, strategy, or judgment. Skip it for simple lookups, mechanical rewrites, and pure tone tasks.

2026-07-1911

cloudflare

sanand0/scripts

For CloudFlare development, deployment, e.g. Python CloudFlare Workers

2026-07-1611

demos

sanand0/scripts

Use when creating demos or POCs

2026-07-1611

name	vitest-dom
description	Use vitest + jsdom for fast, lightweight unit tests for front-end apps

Use vitest and jsdom for front-end testing.
Avoid vitest.config.*; default ESM import works, launch via "test": "npx -y vitest run" in package.json. Add jsdom as a devDependency. Add npm test to prepublishOnly
Treat tests as lightweight integration, not unit. Load the full HTML + scripts and verify real DOM mutations; ensures refactors don't silently break UI wiring.
Log browser console.* output.
Mount local HTML. settings.fetch.virtualServers = [{url:"https://test/", directory: <root>}]. Use page.goto("https://test/...") to load files without a dev-server.
Create a fresh page for each test to isolate window, document, etc.
Fake timers for deterministic testing.
- Call vi.useFakeTimers() in beforeAll, vi.useRealTimers() in afterAll.
- Re-bind window.setTimeout = setTimeout so app code sees the mocked clock.
- Drive async paths with vi.advanceTimersByTime(ms) instead of await sleep.
Stub external APIs with vi.fn() - e.g. window.fetch = vi.fn(() => Promise.resolve({ok:true,...})) avoids network and lets you assert payloads.
Spy on side-effects - vi.spyOn(console, "error"), clipboard reads, etc.; always mockRestore() afterwards to prevent bleed-through.
Add timeouts per test case, e.g. { timeout: 10_000 }, for long-running tests.