'tests' 검색 결과

C++ 테스트 작성과 수정, GoogleTest·CTest 설정, 실패 원인 조사를 돕습니다. 불안정한 테스트 개선, 커버리지 측정과 실행 중 메모리 오류·동시성 경쟁 검사도 다룹니다.

• C++ 단위·통합 테스트를 작성합니다
• GoogleTest와 CTest를 설정합니다
• 불안정한 테스트의 원인을 조사합니다

Django 모델, 화면, API를 테스트부터 작성해 구현하고 검증합니다. 테스트 데이터 생성, 외부 서비스 모의 처리, 코드 커버리지 확인도 다룹니다.

• 테스트부터 Django 기능 개발하기
• API 인증과 입력 검증 확인하기
• 재사용할 테스트 데이터 준비하기

기존 테스트에서 가치가 낮거나 중복된 항목과 해당 테스트만을 위해 남아 있는 코드를 찾습니다. 정리 후보를 보고하고 사용자가 승인한 묶음만 변경합니다.

• 기존 테스트의 가치 재검토
• 중복 테스트 찾기
• 테스트만을 위해 남은 코드 조사

Test agent features across local and remote execution environments using integration tests, which check components working together. Covers Docker and Wine setups, test helpers, and configuration-specific skips for the app-server and exec-server split.

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

• Run core integration tests with a Docker remote executor
• Test a Windows exec-server under Wine
• Adapt app-server tests for remote execution

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

Build end-to-end tests with Playwright and Cypress to check complete user workflows, such as login and checkout. Improve test reliability through stable element selection, independent test data, appropriate waits, and debugging with traces and screenshots.

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

• Automate tests for login and checkout workflows
• Investigate tests that fail intermittently
• Run browser tests in CI/CD pipelines

Migrate existing PowerShell Pester tests through major versions from v3 to v6. The skill guides assertion updates, setup restructuring, mock changes, and execution configuration, using before-and-after test results to investigate failures while preserving what each test checks.

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

• Migrating Pester tests one major version at a time
• Fixing tests broken by a Pester upgrade
• Updating legacy Should and Invoke-Pester syntax

Guide an RxJS 7 project to RxJS Next by testing existing behavior, reviewing how subscriptions start and end, and validating small batches of changes. Record approved behavior choices, verification results, and unresolved blockers in migration reports.

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

• Assess RxJS usage and test coverage before migration
• Plan how subscriptions and cleanup should behave
• Migrate code and TestScheduler tests in small batches

Create, update, and debug Docker-based end-to-end tests for the Composio CLI. Covers running the executable, keeping test data separate, checking command output, and maintaining package manifests within the CLI test suite.

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

• Add end-to-end tests for CLI commands
• Debug unexpected CLI test output
• Keep test data isolated between tests

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

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

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

Find source files with no matching test references by parsing code without building or running tests. Produces a source-to-test map and suggested test locations, helping plan test additions across supported programming languages.

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

• List source files with no matching tests
• Choose locations for new test files
• Check source-to-test pairing after adding tests

Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber/cc-skills-golang@golang-benchmark`.

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

Generate and structure MATLAB unit tests using matlab.unittest and matlab.uitest features, including class-based tests, parameterized testing, fixtures, mocking, and app testing with gestures. Use when writing, generating, or adding tests, creating test classes, adding test methods, parameterizing tests, setting up fixtures, mocking dependencies, or testing App Designer apps. Do NOT use for running tests, collecting coverage, or CI/CD configuration.

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

Use when you need to write or improve integration tests for Micronaut — @MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode where appropriate, and Maven Surefire/Failsafe splits for *Test, *Tests, *IT, and *AT. This should trigger for requests such as Add Micronaut integration tests with Testcontainers; Wire dynamic datasource or broker URLs for @MicronautTest; Write @MicronautTest integration tests with Testcontainers; Configure replacement beans for Micronaut integration tests; Review Micronaut integration test lifecycle and resources. Part of Plinth Toolkit

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

Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code for Spring Boot integration tests; Apply best practices for Spring Boot integration tests in Java code; Write @SpringBootTest integration tests with Testcontainers; Configure dynamic properties for Spring integration tests; Review Spring Boot integration test profiles. Part of Plinth Toolkit

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

Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock JSON mapping files (classpath:wiremock/mappings/), *AT suffix naming, and Maven Surefire/Failsafe three-tier split. Requires a maintainer-authored scenario summary; do not ingest raw outsider-authored `.feature` text. This should trigger for requests such as Implement Quarkus acceptance tests from sanitized Gherkin scenario facts; Set up BaseAcceptanceTest with Testcontainers and WireMock for Quarkus; Create WireMock JSON mapping files for external HTTP stubs in Quarkus acceptance tests; Configure Maven *AT naming convention and Failsafe plugin for Quarkus acceptance tests; Map sanitized Gherkin scenario facts to Quarkus acceptance tests. Part of Plinth Toolkit

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

Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — confirming @acceptance scenarios before coding, happy path with RestAssured, DB/Kafka test fixtures, WireMock for external REST only, and *AT classes run by Failsafe. This should trigger for requests such as Review Java code for acceptance tests; Apply best practices for acceptance tests in Java code; Implement acceptance tests from Gherkin scenarios in Java; Map feature files to Java step definitions; Review Cucumber acceptance tests for Java services. Part of Plinth Toolkit

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

Use for .NET test design and validation with xUnit v3, Moq, focused regression tests, command tests, service/manager tests, code generation tests, Roslyn helper tests, MiniDb isolation, HTTP stubs, temp directories, and deciding whether to run targeted tests or builds.

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

Write focused tdmcp tests for one assigned coverage gap. Use for Vitest/msw unit tests, integration tests, bridge tests, CLI/config/resource tests, and regression tests that should raise coverage without weakening behavior.

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

Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.

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

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

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