테스트·보안 스킬

Test Temporal workflows in Python with pytest. Use time skipping to avoid long waits, replace activities with controlled test versions, and replay execution histories to check that workflow changes remain consistent with previous runs.

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

• Testing long-running workflows without waiting
• Testing workflow logic with mocked activities
• Checking workflow changes against execution histories

Build Solidity contract tests with Hardhat and Foundry. Check individual functions, contract interactions, gas usage, and varied inputs, and use a local copy of mainnet state to test against existing contracts.

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

• Testing token transfers and expected failures
• Checking edge cases with varied generated inputs
• Testing interactions with existing mainnet contracts

Guide web app testing with screen readers such as VoiceOver, NVDA, and JAWS. Check forms, dialogs, keyboard navigation, and spoken update notifications to identify accessibility problems across desktop and mobile browser combinations.

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

• Checking form labels and error announcements
• Testing dialog focus behavior
• Verifying announcements for changing content

Audit websites against WCAG 2.2, guidelines for making web content accessible. Combine automated checks with manual verification to identify barriers, prioritize issues by impact, and guide fixes to page structure and interactive components.

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

• Audit a website for accessibility barriers
• Review keyboard access and form labels
• Fix contrast and heading structure issues

Identify a project's existing test tools and conventions, then run the smallest useful test suite for a specific change. Add or update tests when authorized, and report commands, results, and remaining gaps without overstating coverage.

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

• Run relevant tests for a specific code change
• Identify existing test tools and conventions
• Add or update tests with authorization

Check that an actual app, API, or command-line tool works by exercising its real entry point with realistic inputs. Collect observable evidence such as outputs, logs, exit codes, or screenshots, and report remaining uncertainty.

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

• Checking app behavior through the actual interface
• Verifying API behavior with realistic inputs
• Collecting command-line outputs and exit codes

Review concrete code for exploitable security defects, including missing access checks, unsafe input handling, and exposed secrets. Report verified issues with file locations, reachable attack paths, severity, and suggested fixes.

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

• Review a code change for exploitable vulnerabilities
• Check authentication and access controls
• Trace unsafe input handling and secret exposure

Test a local web app in a real browser, checking the page structure, console messages, and network activity. Follow controls observed on the page and record evidence showing whether the tested flow passes or fails.

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

• Verify a web app flow in a real browser
• Check page state, console messages, and network activity
• Record evidence of test results

Verify Codewhale changes with checks matched to their scope and risk. Collect actual test counts, automated limit checks, and command output to show what passed, what failed, and what remains unverified.

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

• Verify a fix before marking it complete
• Choose tests for the changed area
• Check limits and consistency rules enforced by CI

Builds and installs Codewhale with a source revision identifier, then verifies the installed version in a fresh shell. It guides hands-on runtime checks for interface behavior, routing, approvals, and other changes that automated tests may miss.

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

• Verifying terminal interface changes in the actual product
• Installing and checking a local release build
• Checking model routing and approval behavior

Check Codewhale release readiness through ordered tests, builds, version checks, and manual terminal checks. Record command results and observed behavior, including responsiveness, route isolation, and follow-up input handling, while explicitly identifying any skipped checks.

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

• Run automated checks on the actual release branch
• Check whether a PR merges into the release branch
• Manually test terminal responsiveness and input behavior

Write and fix Java integration tests using Testcontainers 2.x to run real databases and other dependencies in containers. Covers startup checks, container lifecycles, test data isolation, CI setup, and migration from version 1.x.

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

• Adding integration tests with a real database
• Fixing container startup and connection failures
• Sharing containers while isolating test data

Audit and repair existing Cypress tests that fail intermittently. The skill identifies fixed delays, fragile command chains, shared state, and version compatibility issues, then guides targeted changes and repeated test runs to check the results.

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

• Investigating Cypress tests that fail only in CI
• Replacing fixed delays with meaningful conditions
• Diagnosing detached DOM errors

Update Pester test assertions, checks of expected results, from classic v5 syntax to v6 Should-* commands. Identify behavior changes involving booleans, empty values, and collections, then verify the suite and report conversions needing human judgment.

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

• Convert assertions in PowerShell test files
• Adopt Should-* syntax one file at a time
• Review boolean, empty-value, and collection checks

Turn a browser scenario into a Playwright TypeScript test by first performing its steps through Playwright MCP. The skill saves the generated test in the tests directory, runs it, and revises it until it passes.

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

• Create an automated test from a browser scenario
• Turn an executed interaction flow into test code
• Run and fix a generated Playwright test

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

Analyzes one .NET project to plan integration tests for an Oracle-to-PostgreSQL migration. Identifies database access methods, prioritizes migration risks, and documents test cases, seed data, and coverage, including empty strings, NULL values, and timezone behavior.

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

• Identifying database access methods that need integration tests
• Prioritizing tests for Oracle-specific behavior
• Planning checks for empty strings, NULL values, and timezones

Explore a website with Playwright MCP by interacting with three to five key features or user flows. Document actions, interface elements and how to locate them, then generate test cases from the findings.

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

• Exploring a website's main features before designing tests
• Recording interface elements, actions, and expected outcomes
• Creating test cases from observed user flows

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

Review source code for MCP, a protocol connecting AI applications to tools. Check authentication, input validation, unsafe execution, and other security risks, then report findings with file and line references and separate manual follow-ups.

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

• Reviewing an MCP server before release
• Checking authentication and validation on a network-exposed server
• Auditing tool code for unsafe execution paths

Review MCP configurations for exposed credentials, risky command patterns, and package versions that can change unexpectedly. Produce a report with severity levels and suggested fixes without running the commands defined in the configuration.

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

• Reviewing .mcp.json before committing changes
• Checking a new MCP server before adoption
• Finding hardcoded credentials in configurations

Write focused Java unit tests with JUnit 5, including tests that repeat checks across different inputs. Covers clear test structure, exception checks, mock objects that replace dependencies, and ways to organize test suites.

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

• Writing a unit test for a Java method
• Checking the same behavior with multiple input values
• Testing exceptions and related assertions

Check an MCP server before release through a real client session. Compare available features with source code and documentation, test invalid requests and installation, and produce a verdict backed by reproducible commands and responses.

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

• Checking an MCP server before release
• Comparing live features with source code and documentation
• Testing invalid requests and error responses

Guide the design and review of software that handles personal data using GDPR engineering practices. Covers minimal data collection, access controls, logging, encryption, retention, deletion, and checks for code changes and infrastructure.

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

• Reviewing APIs and data models that handle personal data
• Checking logs for sensitive information
• Designing retention and user data deletion processes