'fixtures' 검색 결과

Use when creating or updating component fixtures for screenshot testing, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, and common pitfalls.

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

Develop Rust filters for RTK through tests written before implementation. Use real command output as test inputs, check output snapshots and unexpected inputs, verify a minimum reduction target, and complete formatting, linting, and test checks before finishing.

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

• Adding a new RTK command filter
• Checking filtered output against saved snapshots
• Testing empty, malformed, or ANSI-colored input

Keep comparison answers readable in a terminal about 100 columns wide. Limits Markdown tables to four columns with short phrases, and switches to lists or per-item headings when the content needs longer explanations.

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

• Present concise comparisons in a narrow terminal
• Build readable mappings of flags and their effects
• Turn prose-heavy tables into lists

Add a new exchange integration to CCXT using TypeScript and established exchange templates. Follow guidance for unified methods, data conversion, authentication, sandbox settings, recorded API test data, documentation, and checks across generated language implementations.

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

• Add an exchange that CCXT does not yet support
• Convert exchange responses into CCXT's common data format
• Record real API responses for regression tests

Evaluate how Chatbox answers questions about large attachments using synthetic and real documents. Check whether the model retrieves file content when needed, skips retrieval for unrelated requests, and investigate failures through the actual application flow.

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

• Verify retrieval for questions about large attachments
• Test file-related questions without explicit search requests
• Check that unrelated requests skip file retrieval

Create and organize Python tests with pytest. Use reusable setup, mock replacements for external services, controlled test time, and coverage reports to check normal behavior, failures, retries, and interactions between application components.

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

• Add unit and integration tests to Python code
• Replace external services with mocks in tests
• Check retry behavior and time-dependent logic

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

Write focused C# unit tests with XUnit, including tests that run against multiple input datasets. Apply consistent naming, setup, assertions, shared fixtures, and mock dependencies to keep tests readable, independent, and organized.

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

• Set up an XUnit test project for C#
• Test multiple input cases with Theory and data attributes
• Check exceptions and isolate dependencies with mocks

Reproduce Mastra Code bugs with a real model and compare timestamped logs across network, streaming, execution, and terminal interface layers. Use the evidence to locate timing problems, incorrect token rates, flicker, or stuck status displays.

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

• Investigating incorrect token rate displays
• Reproducing intermittent bugs with a real model
• Tracing flicker or stuck status displays

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

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

Capture before and after screenshots of Lite UI changes on a local machine, compare the images, and publish changed screens to a pull request. It also guides screenshot coverage checks and updates to an existing comment.

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

• Show before and after images in a pull request
• Check which screens a UI change affects
• Add a screen to the screenshot catalogue

Create, update, run, and debug shell-based performance scenarios for the but CLI. It separates repository setup from the operation being measured, uses Hyperfine for timing, and guides focused validation and inspection of test output.

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

• Add a performance scenario for a but CLI operation
• Update repository fixtures for an existing benchmark
• Run a short benchmark for one scenario

Maintain LangBot skill assets by organizing operating rules, reference guides, test cases, fixtures, and troubleshooting entries. Check existing material before adding files, keep detailed instructions in one place, and verify that indexes stay current.

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

• Add a skill without duplicating existing guidance
• Organize reference guides and test cases
• Consolidate troubleshooting for shared causes

Create Playwright tests that check user journeys in a browser. The skill organizes reusable page interactions, configures test environments, investigates intermittent failures using execution traces, and supports API mocking, visual comparisons, and automated pipeline integration.

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

• Test login and other browser user journeys
• Investigate tests that fail intermittently
• Replace API responses with controlled test data

Change a running OpenRig setup by adding or removing agent seats, connecting existing sessions, or attaching terminals. Guides checks for roles, startup context, permissions, and session identity so the setup reflects each change correctly.

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

• Add agent seats to a running rig
• Remove seats and clean up remaining references
• Connect an existing session to an OpenRig node

Design and test combat encounters in Three.js action games. Plan arenas, enemy roles, spawn timing, objectives, boss phases, and rewards, then check fairness and difficulty using repeatable starting conditions on desktop and mobile.

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

• Planning combat arenas and enemy combinations
• Tuning enemy waves and boss phases
• Checking attack warnings and recovery opportunities

Build reusable enemy types and attack sets for Three.js action games. Separate enemy definitions from live state, standardize models and hit detection, and validate combat timing, placeholder assets, and desktop and mobile encounters.

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

• Adding enemies through reusable data definitions
• Separating enemy data from live combat state
• Standardizing models and temporary replacements

Test browser games through repeatable game states and short real playthroughs. Check controls, progression, saves, device layouts, and visible feedback, then report bugs with reproduction steps, severity, and browser evidence.

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

• Gameplay checks before release
• Regression testing after game updates
• Touch controls and mobile layout checks

Build and check monsters for Three.js and web action games using shared rules for joints, attachment points, collision shapes, and combat states. Separate visual animation from damage decisions, and provide reproducible checks for attacks and detail-level changes.

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

• Standardizing joints and attachment points across monsters
• Connecting attack timing with collision and damage handling
• Reproducing combat states and attack phase boundaries

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

Maintain model-routing audit golden fixtures and expected outputs.

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

Review pull requests to code-graph-rag, a multi-language code graph parser. Focuses on graph-edge correctness in language parsers, cross-language consistency, and test fixtures that actually exercise the fix.

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

Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, assertions, fixtures, network mocking, auth flows, debugging, and framework recipes for React, Next.js, Vue, and Angular. TypeScript and JavaScript.

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