'vitest' 검색 결과

OpenClaw 테스트의 메모리 증가와 부족 원인을 조사합니다. 측정값과 메모리 객체 기록을 비교해 실제 해제 누락과 테스트 프로세스의 모듈 보존을 구분하고 수정 결과를 검증합니다.

• Vitest 메모리 부족 원인을 조사합니다
• 같은 프로세스의 메모리 기록을 비교합니다
• 해제 누락과 모듈 보존을 구분합니다

Evaluate Vitest tests by the observable behavior and realistic regressions they protect. Guide new test authoring and review existing suites for duplication, dependence on implementation details, and code used only by tests, with evidence for retention or removal.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking the value of a new or changed Vitest test
• Finding overlapping tests that can be consolidated
• Reviewing tests that break during behavior-preserving refactoring

Choose and run checks for TypeScript SDK changes, including type checks, linting, builds, Vitest suites, and tests of complete runtime flows. Also guides writing or adapting CLI tests for Effect v4.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Validate changes to TypeScript packages
• Choose focused checks for a change
• Investigate failing TypeScript CI checks

Write JavaScript and TypeScript tests with Jest, Vitest, and Testing Library. Covers functions, UI components, and APIs, including mock replacements for external services, reusable test data, and setup for automated testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up testing for a new project
• Test functions and API error handling
• Check React component behavior

Explore an existing Vitest 3.2 JSON test report to count results, search failed tests, and inspect file errors. Review original diagnostic details and keep tentative explanations separate from evidence, without launching tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check failure counts in an existing test report
• Search failures by file path or diagnostic text
• Inspect file errors separately from failed assertions

Build and review Cloudflare Durable Objects for applications that retain shared state, such as chat rooms, games, and booking systems. Covers SQLite storage, remote method calls, WebSockets, scheduled work, Workers integration, configuration, and Vitest tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build shared state for chat rooms, games, and bookings
• Implement remote methods, SQLite storage, WebSockets, and alarms
• Configure Workers bindings and migrations

Write and configure unit tests, which check individual pieces of code, using Vitest. Replace dependencies with test substitutes, measure code coverage, compare saved outputs, and organize filtered or parallel test runs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write unit tests for TypeScript code
• Replace functions and timers with test substitutes
• Measure coverage and compare saved outputs

Set up and refine web projects with Vite, a tool for running development servers and building production files. It covers framework integration, environment settings, live code updates, testing configuration, and splitting code to improve loading.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up React, Vue, or Svelte projects
• Configuring environment variables and API proxies
• Splitting production code into smaller files

Vitest 5 (Vite ネイティブテストフレームワーク) リファレンス。 test, describe, it, expect, vi.fn, vi.mock, vi.spyOn, vi.when、 beforeEach / afterEach、test.extend fixtures、test tags / annotations、 coverage (v8 / istanbul)、snapshot、vitest.config.ts、projects (old workspace)、 Vitest Browser Mode (vitest-browser-react, locators, expect.element)、UI モード、bench fixture。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

사용자 조작과 화면 결과를 중심으로 React 컴포넌트와 훅을 테스트합니다. 통신 응답 모의와 접근성 점검을 지원하고 실제 브라우저에서 검증할 범위도 정리합니다.

• React 폼과 컴포넌트 테스트 추가
• 사용자 정의 훅과 비동기 갱신 검증
• API 성공 및 실패 응답 모의

Create Vitest tests for Mastra playground features using MSW to simulate network responses. Exercise the real client SDK, React Query cache, and components with typed sample data to check loading, access conditions, redirects, and errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test loading, empty, and error states
• Check requests controlled by permissions or feature flags
• Verify pagination and query parameters

Create tests for Convex functions with convex-test and vitest, using a backend that runs in memory. Check arguments, return values, authentication, indexes, errors, and scheduled functions without relying on real time or network access.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test Convex function arguments and return values
• Check behavior with different authentication identities
• Cover errors as well as successful requests

Run repository tests using commands suited to Python, Node, or Rust projects. Detect the project setup from its files, run the full suite or a selected target, and show passing results or failure details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Run the full test suite before pushing changes
• Test a specific file or folder
• Use test commands suited to each project

Set up Vitest testing in any project — detects type (Cloudflare Workers, React, Node, library), generates vitest.config.ts, test setup, utilities, and a sample test. Covers mocking patterns, coverage config, workspace setup, Jest migration. Use whenever the user mentions adding tests, setting up Vitest, configuring tests, migrating from Jest, fixing testing infrastructure, or asks 'how do I test this'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Vitest testing framework patterns and best practices. Use when writing unit tests, integration tests, configuring vitest.config, mocking with vi.mock/vi.fn, using snapshots, or setting up test coverage. Triggers on describe, it, expect, vi.mock, vi.fn, beforeEach, afterEach, vitest.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assists with unit and integration testing using Vitest, a Vite-native test runner. Use when writing tests, configuring mocks, setting up coverage, or migrating from Jest. Trigger words: vitest, unit testing, test runner, vi.fn, vi.mock, test coverage, jest replacement.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Maintain visual snapshot tests, which compare rendered images, for Remotion’s web renderer. Update existing tests after implementation changes, or add explicitly requested tests with sample components, preview registration, and documentation updates for supported properties.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Updating existing tests after renderer changes
• Adding an explicitly requested rendering test
• Registering a test fixture for preview

Write integration tests for core error processors by simulating API failures with a mock model. Check retry attempts, changes to conversation messages, and streamed responses, with guidance on test setup and diagnosing empty output.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check retries and message changes after API errors
• Diagnose empty output in streaming tests
• Verify unrelated errors pass through unchanged

Build Vue 3 applications using JavaScript and JSDoc comments that describe data types. Create components and reusable logic, configure Vite, routing, and state management, and check annotations and behavior with ESLint and Vitest.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build Vue 3 interfaces using JavaScript
• Add JSDoc type hints to components and shared logic
• Migrate Vue 2 Options API code to Composition API

Tests a specific Convex feature with sample data and simulated users, without deployment. It checks expected results, rejects unauthorized callers, and verifies that queries return only data belonging to the current user.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verifying a newly implemented Convex feature
• Checking that other users cannot modify owned data
• Testing rejection of unauthenticated requests

Write, review, filter, mock, and debug Core unit tests with the repository's installed Vitest 5 configuration. Use for tests under Core's Vitest include paths, `vi.mock`/spies/timers, jsdom component tests, coverage output, focused reruns, or unit-test failures. Do not use for browser E2E flows or async Next.js Server Components.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Migrate a test suite from one framework to another, incrementally and without losing coverage. Covers Selenium→Playwright, Cypress→Playwright, Jest→Vitest, Mocha→Vitest, and Protractor→Playwright, with parallel CI running, locator/assertion translation, and a coverage-parity track. Use when: "migrate tests," "switch framework," "Selenium to Playwright," "Jest to Vitest," "framework migration." Not for: bulk selector regeneration after a UI refactor on the SAME framework — use selector-drift-recovery. Not for: healing one flaky test at runtime — use test-reliability. Not for: modernizing patterns without changing framework — use ai-qa-review. Related: playwright-automation, cypress-automation, unit-testing, ci-cd-integration, test-reliability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when writing unit tests, mocking dependencies, testing pure functions, or measuring coverage with Vitest. Trigger words: ユニットテスト, 単体テスト, Vitest, モック, テストを書く, カバレッジ, describe, it, expect, vi.mock.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.