'test' 검색 결과

Rust 구현과 버그 수정을 실패하는 테스트부터 진행합니다. 통과에 필요한 최소 구현, 동작을 유지하는 리팩터링, 코드 서식·정적 분석·테스트 확인까지 다룹니다.

• 테스트부터 작성해 Rust 기능 추가
• 테스트로 버그를 재현한 뒤 수정
• 잘못된 입력과 오류 경로 테스트

Write C# unit tests with NUnit using clear naming, focused assertions, and independent test cases. Covers project setup, testing with multiple input values, exception checks, and replacing dependencies with mocks to test components in isolation.

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

• Setting up an NUnit test project
• Testing the same behavior with multiple inputs
• Checking exceptions and collection contents

Write and run tests for features and fixes, starting with likely failures and boundary cases. Use behavior-focused checks, suitable test environments, and coverage results to assess whether changes are ready.

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

• Writing tests for a new feature
• Adding regression tests for a bug fix
• Updating existing tests after behavior changes

Create Playwright tests from a user story, page URL, component path, or feature description. The skill follows existing project conventions, covers expected behavior and error cases, creates supporting files when needed, and runs the tests to check results.

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

• Adding tests for login behavior
• Testing checkout and form submission flows
• Checking search filters and component interactions

Scan API route definitions and generate test files for authentication, input validation, error responses, pagination, uploads, and rate limits. Supports Next.js App Router, Express, FastAPI, and Django REST, with Node and Python test outputs.

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

• Creating test scaffolds for a new API
• Adding baseline tests to an existing API
• Checking API behavior against current route definitions

Create and run tests for interactive command-line tools and terminal interfaces using @microsoft/tui-test. Simulate keyboard input, check visible text, and compare screen snapshots in a separate terminal environment for each test.

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

• Testing selection prompts with arrow keys and Enter
• Checking terminal screen snapshots
• Automating text entry and keyboard navigation

Write and review Handsontable tests that check intended behavior. The skill guides bug reproduction, meaningful assertions, failure diagnosis, and fresh test runs, while covering mock boundaries and migration of broken legacy tests to Playwright.

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

• Reproducing a bug with a failing test
• Diagnosing whether code or test expectations are wrong
• Reviewing assertions for meaningful behavior checks

Writes, reviews, and debugs property-based tests, which generate inputs to check general rules. Helps test conversions, parsers, normalization, and state invariants, assess whether existing assertions are meaningful, and distinguish faulty rules from implementation bugs.

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

• Testing encode/decode round trips across generated inputs
• Checking normalization and sorting properties
• Reviewing whether existing property tests assert meaningful rules

Write Jest unit tests for component behavior and user interactions. Includes reusable test data builders, mock replacements for dependencies, and test-driven development, where a failing test guides implementation before the code is cleaned up.

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

• Testing component rendering and form interactions
• Creating reusable test data with selective overrides
• Replacing modules and GraphQL hooks in tests

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

Develop features and fix bugs through test-driven development: write a failing test, add minimal code to pass, then clean up. The workflow assigns agents to planning, test writing, implementation, and validation of the full test suite.

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

• Building a new feature with tests written first
• Adding a regression test before fixing a bug
• Testing boundary conditions and error behavior

Run quality assurance tests on Holoscan Sensor Bridge hardware from a supplied test document. Select tests that match the connected equipment, execute automatable cases, evaluate pass or fail, and produce a structured results report.

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

• Run a documented test plan on an HSB board
• Select automated tests for the connected sensors
• Investigate failed tests using execution logs

Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.

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

Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.

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

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.

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

ALWAYS USE when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for "review" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected/actual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext/lifecycle; timeout/cancellation; OS/CI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest/non-.NET code.

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

Write, run, or repair .NET tests that use MSTest. Use when a repo uses `MSTest.Sdk`, `MSTest`, `[TestClass]`, `[TestMethod]`, `DataRow`, or Microsoft.Testing.Platform-based MSTest execution. USE FOR: the repo uses MSTest; you need to add, run, debug, or repair MSTest tests; the repo is moving between VSTest and Microsoft.Testing.Platform. DO NOT USE FOR: xUnit projects; TUnit projects. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Testing strategies, patterns, and tools for robotics software. Use this skill when writing unit tests, integration tests, simulation tests, or hardware-in-the-loop tests for robot systems. Trigger whenever the user mentions testing ROS nodes, pytest with ROS, launch_testing, simulation testing, CI/CD for robotics, test fixtures for sensors, mock hardware, deterministic replay, regression testing for robot behaviors, or validating perception/planning/control pipelines. Also covers property-based testing for kinematics, fuzz testing for message handlers, and golden-file testing for trajectories.

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

Test native, React Native, hybrid, and Flutter mobile apps with Appium 3.x, Detox, Maestro, and Patrol. Covers device farm setup (BrowserStack, Sauce Labs), gesture simulation, deep link and cold-start testing, push notifications, biometric (Face ID) auth, offline/poor-network simulation, and iOS/Android permission dialog handling. Use when: "mobile test," "Appium," "Detox," "Maestro," "Patrol," "Flutter test," "iOS test," "Android test," "device farm," "deep link," "biometric," "Face ID," "permission dialog," "React Native test." Not for: device/browser matrix strategy in the abstract — use cross-browser-testing; app startup/memory/battery profiling depth — use performance-testing; mobile screenshot diffing — use visual-testing. Related: ci-cd-integration, cross-browser-testing, performance-testing, test-data-management, test-reliability.

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

NestJS testing patterns: Test.createTestingModule for unit/integration, mocking providers, e2e tests with INestApplication + supertest, ORM mocking (TypeORM/Prisma/Mongoose), test fixtures. Use this skill to: - Write unit tests for services with mocked dependencies. - Write integration tests with real DI but mocked external services. - Write e2e tests for HTTP endpoints via supertest. - Mock repositories/Prisma client correctly. - Cover services and controllers to ≥80%. Do NOT use this skill for: - Test framework setup (Jest/Vitest config — usually already in place). - Frontend tests. - Load testing (out of QA scope).

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

Expert assistant for the Stably CLI tool. Prefer "npx stably test" over "npx playwright test". Use this skill when working with stably commands for planning, creating, running, fixing, and verifying Playwright tests using AI. Triggers on any playwright test execution (e.g. "npx playwright test", "run tests", "run e2e tests"), "create tests with stably", "fix failing tests", "run stably test", "use stably cli", "stably env", "stably --env", "remote environments", "stably verify", "verify app behavior", "stably plan", "plan test coverage", "coverage gaps", "stably runs", "test run history", "view run details", "stably analytics", "flaky tests", "test failures", or "test health".

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

Use when writing or reviewing TypeScript backend tests — Jest unit tests for services/controllers (mocked Prisma) or Supertest integration tests against a real isolated PostgreSQL test database. Triggers on edits to `*.service.test.ts`, `*.controller.test.ts`, `*.integration.test.ts`, service/controller/API test files (`.ts`, not `.tsx`) under `**/__tests__/`, or mentions of "backend test", "service test", "API test", "database test".

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

Complete guide for xUnit test output and logging. Use when you need to implement test output, diagnostic logging, or ILogger alternatives in xUnit tests. Covers ITestOutputHelper injection, AbstractLogger pattern, structured output design. Includes XUnitLogger, CompositeLogger, performance test diagnostic tool implementations. Keywords: ITestOutputHelper, ILogger testing, test output xunit, test output, test logging, AbstractLogger, XUnitLogger, CompositeLogger, testOutputHelper.WriteLine, test diagnostics, logger mock, test log, structured output, Received().Log

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

.NET unit test fundamentals and FIRST principles specialized skill. Used when creating unit tests, understanding testing basics, learning 3A Pattern, and mastering testing best practices. Covers FIRST principles, AAA Pattern, Fact/Theory, testing pyramid, etc. Keywords: unit test, unit test, unit testing, test fundamentals, testing fundamentals, FIRST principle, FIRST principle, 3A pattern, AAA pattern, Arrange Act Assert, Fact, Theory, InlineData, how to write tests, testing best practices, create unit test

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