'test' 검색 결과

ISTQB/JSTQB のテスト設計（test design）活動を支援するスキル。test-analyze が識別したテスト条件から、テスト対象の特性に応じたテスト技法（同値分割・境界値分析・デシジョンテーブル・状態遷移・カバレッジ基準・エラー推測など）を選定提案し、承認された技法で具体的なテストケース（入力値・前提・期待結果）を導出して、設計書 test-design.md（技法選定根拠・カバレッジ）とケース一覧 test-case.md の 2 本を作る。「テストケースを作って」「テストケースを設計して」「どの技法で網羅すべきか提案して」「境界値/デシジョンテーブルでテストを起こして」と依頼されたときに使う。テストコード実装（test-implement）は対象外。単発のテスト作成依頼（単にユニットテストを書きたいだけ）も対象外。/test-design <テスト対象名> で明示的に呼び出されたときのみ使用する。

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

ISTQB/JSTQB のテスト実行（test execution）活動を支援するスキル。test-implement が具体化したテストを実行し、結果を記録し、失敗を欠陥候補として整理して test-execution-log.md にまとめる。自動テストならランナーを実行し結果を解釈、手動テストなら利用者の実施結果を聞き取って記録する。失敗は欠陥候補として整理し、外部 issue 化は提案に留める。「テストを実行して結果を記録して」「テスト実行ログを作って」「失敗を欠陥として整理して」「手動テストの結果を記録して」と依頼されたときに使う。ワークフローの test-targeted（修正範囲にテストランナーを絞り込んで実行するだけ）とは別物で、こちらは ISTQB プロセスとしての実行・記録・欠陥候補整理を成果物 test-execution-log.md に残す。単発のテスト作成依頼（単にユニットテストを書きたいだけ）は対象外。/test-execute <テスト対象名> で明示的に呼び出されたときのみ使用する。

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

AI-driven Flutter E2E testing via VM Service CLI. Control running Flutter apps in debug mode for smoke tests, regression checks, exploratory testing, and UI automation. Trigger when user mentions E2E testing, UI automation, smoke tests, integration testing, test automation, controlling Flutter apps, VM Service interaction, debugging UI flows, automated regression testing, CI sanity checks, or testing native dialogs/permissions/WebViews. Supports stateful named instances or stateless direct URI connections. Ideal for rapid test feedback, AI agent workflows, element discovery, screenshot capture, log collection, and scriptable UI interactions (tap, scroll, enterText). Use for troubleshooting flaky tests, automating repetitive manual tests, verifying app behavior after merges, or setting up automated QA pipelines.

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

Complete guide for Testcontainers NoSQL integration testing. Use when containerized integration testing for MongoDB or Redis. Covers MongoDB document operations, Redis five data structures, Collection Fixture pattern. Includes BSON serialization, index performance testing, data isolation strategy, and container lifecycle management. Keywords: testcontainers mongodb, testcontainers redis, mongodb integration test, redis integration test, nosql testing, MongoDbContainer, RedisContainer, IMongoDatabase, IConnectionMultiplexer, BSON serialization, BsonDocument, document model testing, cache testing, Collection Fixture

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

Complete guide for TUnit new-generation testing framework. Use when creating test projects with TUnit or migrating from xUnit to TUnit. Covers Source Generator driven test discovery, AOT compilation support, fluent async assertions. Includes project creation, [Test] attribute, lifecycle management, parallel control, and xUnit syntax comparison. Keywords: TUnit, tunit testing, source generator testing, AOT testing, new generation testing framework, [Test], [Arguments], TUnit.Assertions, Assert.That, Before(Test), After(Test), NotInParallel, TUnit.Templates, Microsoft.Testing.Platform, TUnit vs xUnit, parallel execution

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

PHPUnit 또는 Pest로 Laravel 기능을 테스트부터 구현합니다. 모델, API, 인증과 권한을 검증하고 외부 서비스를 모의 처리하며 테스트가 실행한 코드 범위를 확인합니다.

• Laravel 기능을 테스트부터 구현합니다
• API 인증과 권한을 검증합니다
• 결제, 메일과 큐를 모의 처리합니다

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 Vitest tests for Mastra playground features using MSW to simulate network responses. Exercise the real client SDK, React Query cache, and components with typed sample data to check loading, access conditions, redirects, and errors.

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

• Test loading, empty, and error states
• Check requests controlled by permissions or feature flags
• Verify pagination and query parameters

Set up Playwright, a browser testing tool, for an existing web project. Generate configuration, test folders, an example test, and applicable CI automation, then run the test and address setup failures.

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

• Adding browser tests to an existing web project
• Configuring tests for the project's framework
• Running browser tests automatically in CI

Trace failing cmux Swift package tests to the commits that introduced them by running older revisions in CI, the automated testing environment. It helps distinguish outdated expectations, code regressions, and intermittent failures, then guides focused fixes and verification.

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

• Investigating a package suite failing on main
• Finding the PR that first broke a test
• Distinguishing outdated tests from code regressions

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

Run concurrent Omnigent conversations with real hosts and runners while replacing the LLM with a zero-latency mock. Read the generated report to explain response-time distributions, throughput, and failures, helping assess Omnigent's own processing overhead.

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

• Measuring performance with concurrent hosts
• Studying latency as conversation history grows
• Comparing throughput and failures under load

Add tests to a completed development phase using its records and implementation. Review the proposed coverage, then generate unit tests for individual components and browser tests for full workflows, verify them, and commit the test files.

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

• Adding automated tests after a development phase is complete
• Turning acceptance criteria into test coverage
• Reviewing which code needs unit or browser tests

Write and review Go tests using patterns suited to functions, file operations, and terminal interfaces. Cover multiple scenarios, check state changes, and compare rendered output with saved expected results while keeping slow integration tests separately skippable.

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

• Testing Go functions and parsers across multiple cases
• Checking file operations in temporary directories
• Testing Bubbletea state changes and interactions

Turn Trail of Bits Testing Handbook content into Claude Code skills for security testing. Creates or refreshes SKILL.md files using templates for tools, fuzzers, techniques, and subject areas, then validates structure and links between skills.

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

• Generate security testing skills from handbook sections
• Refresh a skill after handbook updates
• Create multiple skills from handbook content

Assess test strength by introducing deliberate code changes with mewt or muton. Configure test runs, examine changes that tests miss, distinguish harmless equivalents from testing gaps, and investigate potential bugs in the affected code.

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

• Set up and scope a mutation testing run
• Investigate code changes that tests fail to detect
• Distinguish equivalent changes from testing gaps

Design tests for charts, dashboards, and interactive diagrams. Combine data checks, component tests, screenshot comparisons, and end-to-end workflows to catch incorrect values, broken interactions, and visual changes while keeping tests stable.

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

• Choose test coverage for a chart component
• Set up stable screenshot comparisons for a dashboard
• Verify mobile interactions and degraded network states

Review regression coverage and test quality in Apache Pinot when behavior or tests change. Use it to assess whether code changes and bug fixes have relevant tests, including paths that handle different types or null values.

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

• Reviewing added or modified test files
• Checking production changes without test updates
• Checking regression tests for bug fixes

Assess whether tests detect the wrong behavior relevant to a specific change, PR, or commit. Link findings to exact revisions, compare faulty and correct behavior when execution is authorized, and distinguish observed results from predictions.

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

• Check whether a regression test detects the original bug
• Assess tests for a new feature
• Review behavior preservation during a refactor

Check the TestDino connection and personal access token, then discover accessible organizations, projects, and available modules. Use the results to identify the correct projectId before starting project-specific work.

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

• Check the TestDino connection
• Validate a personal access token
• Find accessible organizations and projects

Write Python tests with Hypothesis that generate varied inputs and check properties, rules that should always hold. Discover edge cases, reduce failures to simpler examples, and save failing inputs for replay alongside conventional tests.

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

• Finding edge cases in parsers and input handling
• Checking mathematical properties across many inputs
• Testing data encoding and decoding round trips

Add and run unit or functional tests for Megatron-LM. The guide explains test organization, YAML execution recipes, reference results for numerical checks, test filters, temporary disabling, and reproducing continuous integration failures locally.

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

• Add unit tests or functional training tests
• Run selected tests and reproduce CI failures locally
• Download or update reference results for numerical checks

Run automated release testing (UI or API) via the AWS DevOps Agent using a pre-configured test profile. Use when the user wants to validate multi-step workflows, verify features, check for regressions, or test API endpoints. Trigger words include run tests, UAT, test my app, test profile, UI test, API test, automated testing, regression test, QA, end-to-end test, run the QA agent.

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

Plan and run usability tests on existing or prototype designs including test design, task scripts, moderation, observation, and findings synthesis. Use this skill whenever the user wants to test usability, run a moderated test, run an unmoderated test, validate a design, find usability issues, or improve task completion. Triggers on usability test, usability testing, moderated test, unmoderated test, task script, think aloud, prototype testing, user testing, design validation, task completion. Also triggers when the user has built something and wants to know if real users can use it before shipping.

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