'vitest' 검색 결과

Analyze the full retained history of one NemoClaw pull request to identify contributor, review, and automation delays. Generate a summary and an interactive timeline file, then compare observed timing with a default ten-minute target or a requested alternative.

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

• Find delays across a pull request's lifetime
• Compare processing time with a target
• Measure review and merge waiting time

Coordinate large code migrations in reviewable batches. The agent changes local files, while the Composio CLI connects tracking issues, pull requests, and automated checks so each batch can be tested and reviewed before proceeding.

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

• Upgrading frameworks across many files
• Renaming an API throughout a monorepo
• Migrating configuration files or test tools

Maintain data retention in ClawHub's Convex tables by classifying each table, defining expiration fields, and bounding cleanup jobs. Guide changes to temporary data and expired authentication records, with focused tests and runtime verification.

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

• Classify retention policies for new tables
• Add expiration fields and indexed cleanup
• Update scheduled jobs with bounded deletion batches

Suggests running verbose shell commands through RTK, a tool that condenses command output, and executes them after confirmation. It helps reduce the text an AI agent processes when reviewing Git history, tests, builds, and files.

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

• Reducing output when reviewing Git history and diffs
• Condensing long test and build results
• Reading large files with less command output

Prepare a branch for a pull request by running local tests, checking types for Node projects, pushing commits, and showing the CI pipeline link. Failed checks stop the workflow before the push.

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

• Running tests before opening a pull request
• Checking Node types before pushing commits
• Getting the CI link after a push

Set up JavaScript and TypeScript projects using Anthony Fu’s conventions for code organization, development tools, and package publishing. Establish shared checks for formatting, types, unused code, and tests before committing changes.

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

• Setting up a new TypeScript project
• Standardizing formatting and code checks
• Managing dependencies across a monorepo

Provide language-specific reference files for test analysis skills. The catalog helps agents recognize test methods, assertions, skipped tests, waiting patterns, setup and cleanup hooks, external dependencies, and tagging capabilities across different frameworks.

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

• Looking up assertion syntax for a test framework
• Checking skip annotations and setup or cleanup hooks
• Supporting test analysis across multiple languages

Classify existing tests with standard tags for success cases, errors, boundaries, and other behaviors. Get a per-test mapping and distribution summary, or apply tags using supported framework syntax and verify compilation and test discovery.

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

• Comparing success-case and error-case test counts
• Adding standard tags to existing tests
• Reviewing the mix of boundary and integration tests

Develop features, fix bugs, and refactor code by writing tests before implementation. The workflow combines unit, integration, and end-to-end tests of complete user flows, with an 80% coverage requirement and checks for errors and boundary cases.

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

• Build a new feature from user journeys
• Write a test that reproduces a bug before fixing it
• Refactor existing code while keeping tests passing

Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.

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

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

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

按 tdesign-vue-next 规范编写、补充、迁移或审查 Vue 组件单元测试，并运行 Vitest 验证。适用于 packages/components 下的组件 API 测试、Issue 回归测试，以及相关 hooks、utils 测试。

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

Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

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

Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or similar.

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

Writes Vitest tests following project patterns: __tests__/ directories, vi.mock() for module mocking with vi.hoisted() for test-time factories, global LLM mock from src/test/setup.ts, environment variable save/restore in beforeEach/afterEach, vi.clearAllMocks() lifecycle, and test file organization. Use when user says 'write tests', 'add test coverage', 'test this', creates *.test.ts files, or when test failures appear in CI. Do NOT use for non-test code or for debugging without writing tests.

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

Review generated or changed test code against universal testing rules before it ships. Best used reactively after an agent writes, edits, generates, or refactors tests, before presenting, committing, or merging them. Use for pytest (test_*.py, *_test.py), PHPUnit/Pest (*Test.php), Jest/Vitest (*.test.ts, *.spec.js), Go (*_test.go), files under tests/, __tests__/, or spec/, and review requests like 'write tests for X', 'add tests', 'test this', 'review these tests', or PR diffs containing tests. Can also guide test writing when explicitly invoked before the work. This skill is the quality gate that prevents AI-generated test bloat. DO NOT USE for production or implementation code review (use clean-code-guard), CI or test-runner configuration, running or debugging tests, or general architecture discussion.

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

Writes turn-level tests for a LiveKit agent in the user's normal test suite: pytest (Python) or Vitest (Node.js). Use when the user asks to "write tests for my agent", "add a test for this tool", "test the handoff", "pin this bug", "why does my agent test fail", or after building or changing agent behavior that needs regression coverage. Covers the SDK's test session harness, assertions on messages, tool calls and handoffs, LLM judging of a reply against an intent, mocking tools, multi-turn tests, and judging whole conversations with the built-in judges. For interactive poking use debugging-livekit-agents. For grading whole conversations at scale use running-livekit-simulations.

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

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

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

A skill for writing and maintaining unit tests for TDesign React components using Vitest, including testing patterns, best practices, and snapshot testing.

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

Guide red-green-refactor TDD with test generation, coverage-gap analysis, and multi- framework support. Use when writing tests first, analyzing coverage, generating test stubs, or converting tests between Jest, Pytest, JUnit, and Vitest.

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

Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.

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

Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects. Use when testing components with RTL, mocking APIs with MSW, or creating Playwright user flow tests.

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

ALWAYS USE for test work that requires changes: write, add, generate, repair, or strengthen tests for existing code in xUnit, MSTest, NUnit, pytest, Vitest/Jest, Go, or another framework. Includes regression cases, failing or flaky tests, coverage-driven additions, and audit-then-fix requests. Focused work stays direct; broad or multi-stage work invokes test-engineer. DO NOT USE for only running tests, analysis-only audits, framework/platform migrations, a test blocked on a missing production seam (testability-obstacle), or MSTest API/configuration corrections that do not design new cases (writing-mstest-tests). Within an active test-engineer pipeline, reuse supplied guidance and do not re-enter this skill.

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

Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging). Read this catalog to discover available extension files (e.g., dotnet.md for .NET/MSTest/xUnit/NUnit/TUnit, python.md for pytest/unittest, typescript.md for Jest/Vitest/Mocha, java.md for JUnit/TestNG, etc.). Do not invoke this reference-only skill — its bundled files are read by the quality agent and analysis skills needing framework-specific lookup tables (test markers, assertion APIs, skip annotations, sleep patterns, mystery guest indicators, integration markers, setup/teardown, tag-support capability).

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