'jest' 검색 결과

Improve existing code through repeated cycles of testing, implementation, and refactoring. The skill covers performance bottlenecks, error recovery, code coverage, and documentation, helping developers refine behavior and structure while keeping tests passing.

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

• Refactoring existing code while keeping tests passing
• Adding tests before implementing expected behavior
• Investigating slow database access and cache usage

요구 사항 정리부터 설계, 테스트 우선 구현, 검토, 배포까지 단계별로 진행합니다. Claude Flow로 여러 에이전트의 역할을 나누고 개발 전반을 관리합니다.

• 요구 사항부터 새 기능 개발
• 테스트와 함께 기존 코드 개선
• 버그 조사와 재발 방지 테스트 추가

Explicitly save debugging discoveries, project conventions, and working preferences to Claude's persistent project memory. The skill checks for duplicate notes, keeps entries concise, and suggests moving enforceable rules into CLAUDE.md when appropriate.

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

• Preserving hard-won debugging discoveries
• Recording undocumented project conventions
• Remembering tool-specific commands and pitfalls

Maintain existing tests for Walkontable, Handsontable's table rendering engine. The skill explains its separate test commands and covers frozen rows and columns, visible area calculations, scroll alignment, and pitfalls that can hide failures or produce misleading results.

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

• Maintaining existing Walkontable rendering tests
• Checking frozen rows and columns during scrolling
• Testing visible areas after container resizing

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

Create unit, integration, and E2E tests that check complete user flows, then identify coverage gaps and investigate unreliable results. The skill also supports performance and security test plans, with findings organized by severity and suggested fixes.

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

• Writing tests for normal behavior, errors, and boundary values
• Finding gaps in test coverage
• Investigating tests that fail intermittently

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

Find language-specific guidance files for a code-testing pipeline. This reference catalog points agents to build and test commands, mocking patterns, common errors, and selected workflow examples across languages including .NET, Python, TypeScript, Go, and Java.

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

• Finding test guidance for a project's programming language
• Locating build commands and test framework guidance
• Finding mocking patterns and common error references

Document project-specific development rules for an AI agent using a starter template. It provides sections for error handling, testing, code style, file organization, examples, and practices to avoid, ready to fill with actual conventions.

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

• Documenting project-specific development rules
• Organizing testing and error-handling conventions
• Recording code examples and practices to avoid

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

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.

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

Write tests using React Native Testing Library (RNTL) v13 and v14 (`@testing-library/react-native`). Use when writing, reviewing, or fixing React Native component tests. Covers: render, screen, queries (getBy/getAllBy/queryBy/findBy), Jest matchers, userEvent, fireEvent, waitFor, and async patterns. Supports v13 (React 18, sync render) and v14 (React 19+, async render). Triggers on: test files for React Native components, RNTL imports, mentions of "testing library", "write tests", "component tests", or "RNTL".

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

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.

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

Gates whether a new test should exist and forces it to be efficient, protecting CI from low-value test bloat. Use before any change to what a pytest, Jest, or Playwright test asserts or sets up, down to one fixture or one assertion added to an existing block. Front-loads the value bar (every test must catch a realistic regression no existing test already catches; extend the nearest existing test before writing a new standalone one; test behavior through the public interface, not implementation details; collapse near-duplicates into parameterized cases) and the efficiency bar (deterministic, isolated, fast; pick the cheapest test level; Django TestCase over TransactionTestCase; no sleeps, no real network; no time bombs from absolute dates left to age against the real clock; no database a test never uses). Includes a "don't write it" decision tree. For fixing an existing flaky test use `/fixing-flaky-tests`; after this gate says a Playwright test is warranted, use `/playwright-test` for mechanics.

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

Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when `hogli ci:insights` or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a flaky job, when asked to check Trunk Flaky Tests for a test, PR, or master, or when asked to deflake, stabilize, or fix a flaky Jest, pytest, or Playwright test. Core discipline: reproduce locally before changing anything, fix the root cause (never mask it with sleeps, retries, or bigger timeouts), and prove the fix with an N-run validation loop sized to the observed failure rate. Stabilizing is not the only valid outcome — the skill also gates whether the test should exist, so deleting a test that catches nothing real, or re-leveling one that flakes because of the level it runs at, are first-class endings.

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

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.

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

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.

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

Configure development tools, linting, formatting, and test runners for existing JavaScript projects. Use for ESLint, Prettier, Jest, or equivalent tool setup; defer application implementation and generic project scaffolding.

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

Write Unit and E2E tests with Jest, mocking strategies, and database isolation in NestJS. Use when writing NestJS unit tests, E2E tests with supertest, or mock providers.

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

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).

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

Analyze assertion quality, depth, variety, and false confidence in existing tests. ALWAYS USE when asked about weak, shallow, trivial, always-true, self-referential, assertion-free, presence/truthiness-only, or insufficiently diverse assertions, including MSTest, Jest, pytest, and Go. DO NOT USE for direct fixes: writing-mstest-tests owns supplied MSTest assertions; code-testing owns new cases. Use test-gap-analysis when asked whether tests would catch a production change, and test-anti-patterns for general severity-ranked audits.

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