'jest' 검색 결과

Write JavaScript and TypeScript tests with Jest using consistent structure, dependency mocking, and checks for asynchronous code. Includes guidance for snapshots and React components, focusing on user interactions, accessibility, and choosing appropriate assertions for expected results.

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

• Organize Jest test files and test names
• Replace API or database dependencies with mocks
• Test asynchronous results and errors

Jest best practices, patterns, and API guidance for JavaScript/TypeScript testing. Covers mock design, async testing, matchers, timer mocks, snapshots, module mocking, configuration, and CI optimization. Baseline: jest ^30.5.2. Triggers on: jest imports, describe, it, test, expect, jest.fn, jest.mock, jest.spyOn, mentions of "jest", "unit test", "test suite", or "mock".

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

Write and update Handsontable unit tests with Jest and type tests with TypeScript. Explains file placement, focused test runs, boundary cases, and checks for public types, while helping choose between isolated logic tests and browser tests.

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

• Adding unit tests for calculations and data transformations
• Covering bug fixes and internal refactoring
• Checking TypeScript declarations and public exports

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

Creates test starters for React and Next.js applications and analyzes coverage reports to find untested code. Supports unit, integration, and browser-based tests, simulated API responses, reusable test data, and test runner configuration.

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

• Generating test starters for React components
• Finding untested code before a release
• Creating browser tests from Next.js routes

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

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

Review how tests use mocks, substitutes for external services or resources. Identify excessive mocking and missing cleanup, suggest more realistic tests, and check whether automated checks consistently catch problems and prevent regressions.

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

• Reviewing tests with too many mocks
• Checking mock cleanup between tests
• Improving realistic API mocks

Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.

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

• Review accessibility coverage for shared components
• Add accessibility checks to page flow tests
• Run accessibility tests in CI

Create unit test scaffolds, sample data, and mocks from code or specifications. Analyze coverage reports to prioritize missing tests, and guide test-driven development through failing tests, minimal implementation, and refactoring.

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

• Create unit tests from existing code
• Prioritize gaps in test coverage
• Turn acceptance criteria into tests

Develop and modify the Handsontable Angular wrapper with guidance on component lifecycle, settings updates, and NgZone, which controls change detection. It also covers standalone examples, global configuration, and the build and test workflow.

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

• Fix settings updates in the Angular wrapper
• Review change detection around grid operations
• Update examples to standalone components

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

Testing Angular 18-21: TestBed, component harnesses (@angular/cdk/testing), Karma+Jasmine (default historical) vs Jest (jest-preset-angular, modern), Angular Testing Library (RTL-style). HttpClient mocking via HttpTestingController. NgRx Effects testing. Cypress / Playwright e2e. Use this skill to: - Detect runner (Karma+Jasmine vs Jest) and configure correctly. - Write component tests with TestBed. - Use component harnesses for Material / custom UI components. - Mock HttpClient via provideHttpClientTesting + HttpTestingController. - Test signal-based inputs with componentRef.setInput(). - Test NgRx Effects with provideMockActions. Do NOT use this skill for: - General Angular conventions (see angular-conventions). - Routing patterns broadly (see angular-routing — covers testing routes briefly). - Form patterns broadly (see angular-forms).

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

Testing React Native: Jest with jest-expo / react-native preset, React Testing Library Native, native module mocking, hook testing. Optional sections for Detox (native automation) and Maestro (declarative YAML e2e). Use this skill to: - Configure Jest preset based on workflow. - Write component tests with @testing-library/react-native. - Mock native modules (react-native-reanimated, expo-*, react-native-mmkv). - Test custom hooks via renderHook. - Set up Detox or Maestro for e2e (optional, requires native toolchain). Do NOT use this skill for: - General RN conventions (see rn-conventions). - Web-React testing (see react-plugin:react-testing — different jsdom setup). - Plain Node testing patterns (see nodejs-plugin equivalents).

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

Generate Jest-based unit tests for JavaScript/TypeScript code. Creates test files following Jest conventions with proper mocking, describe blocks, and coverage.

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

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.

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

Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib-* clients, ExC Shell context (@adobe/exc-app), and UIX Guest SDK (@adobe/uix-guest). Use this skill whenever the user mentions testing App Builder actions, writing unit tests for Runtime actions, creating integration tests, mocking Adobe SDKs, setting up test fixtures, running aio app test, or wants to verify action behavior before deployment. Also trigger when users mention Jest configuration for App Builder, test coverage, CI test setup, React component test, Testing Library, UI test, Provider wrapper, test my page, test my form, test my table, test my component, mock shell context, mock extension context, debug test failures, or fix Jest errors.

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

Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib-* clients, ExC Shell context (@adobe/exc-app), and UIX Guest SDK (@adobe/uix-guest). Use this skill whenever the user mentions testing App Builder actions, writing unit tests for Runtime actions, creating integration tests, mocking Adobe SDKs, setting up test fixtures, running aio app test, or wants to verify action behavior before deployment. Also trigger when users mention Jest configuration for App Builder, test coverage, CI test setup, React component test, Testing Library, UI test, Provider wrapper, test my page, test my form, test my table, test my component, mock shell context, mock extension context, debug test failures, or fix Jest errors.

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

의료 앱 공개 전에 진료 판단 지원 로직, 환자 정보 유출, 데이터 무결성 등을 검증하는 스킬입니다. 중대한 테스트가 실패하면 배포를 중단하는 구성을 제시합니다.

• 전자 의무 기록 공개 전 검증
• 약물 상호작용과 투여량 검증 변경 확인
• 권한 변경 후 환자 정보 유출 확인

Create integration tests for syncable metadata entities in Twenty itself. Cover invalid inputs, validation errors, and successful data operations, using reusable GraphQL request helpers, error snapshots, and cleanup routines to organize the test suite.

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

• Add integration tests for a new syncable entity
• Test required fields, duplicates, and invalid references
• Verify successful creation, updates, and deletion

Develop and modify the Handsontable wrapper for Vue 3 with guidance on component structure, settings updates, column configuration, and shared data references. It also explains the build order and tests used to check wrapper changes.

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

• Fix settings updates in the Vue 3 wrapper
• Modify per-column configuration
• Investigate how array changes reach the grid

Build, debug, and refactor JavaScript applications for browsers and Node.js. Covers asynchronous tasks with async/await, module organization, performance checks, and test creation, with explicit error handling and modern ES2023+ syntax.

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

• Build a vanilla JavaScript application
• Fix errors in asynchronous API requests
• Organize code into ESM modules

Generate tests for a specified file or module using the project’s testing conventions. Cover expected behavior, unusual inputs, boundaries, failures, and external interactions, with independent tests and mock substitutes for external dependencies.

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

• Add tests for existing functions or modules
• Check empty inputs and boundary values
• Test failures in APIs, databases, and file operations

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

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

Testing for React/Next.js with Jest, React Testing Library, and Playwright. Use when generating tests, writing unit tests, analyzing coverage, scaffolding E2E tests, configuring Jest, or improving test quality.

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