'assertion' 검색 결과

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

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 C# unit tests with TUnit using clear test structure, asynchronous checks, and multiple input cases. Get guidance on setup and cleanup, execution controls, test organization, and converting existing xUnit tests to TUnit.

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

• Setting up a TUnit test project
• Testing one behavior with multiple input cases
• Organizing test setup and cleanup

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

Review and improve .NET/C# code against project conventions. Cover public API documentation, dependency injection for supplying services to classes, asynchronous operations, tests, configuration, logging, and input validation, including guidance for Semantic Kernel integrations.

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

• Review C# code against project conventions
• Improve XML documentation for public APIs
• Review asynchronous operations and dependency injection

Write and register SGLang unit and end-to-end tests, from choosing models and file locations to reusing server fixtures. Follow project rules for meaningful assertions, CI registration, dependency mocking, and safe server cleanup after tests.

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

• Adding CPU-only unit tests for component logic
• Testing features through a running SGLang server
• Registering tests in an appropriate CI suite

Investigate CUDA crashes in SGLang using logs and inputs saved before execution. Inspect tensor shapes, data types, and numerical anomalies, with guidance for separate process logs and additional CUDA debugging tools.

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

• Investigating illegal memory access and device-side assertions
• Tracing NaN or Inf values through kernel calls
• Saving inputs before a CUDA crash

Rewrite lengthy prompts, tool descriptions, and agent instructions into compact text while preserving requirements, exceptions, and exact values. The process records removed content and compares token counts, the units models use to measure text length.

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

• Shortening system prompts
• Compressing tool documentation and skill bodies
• Reducing text length for model input

Approach engineering problems by checking assumptions, defining performance constraints, and choosing suitable tools before implementation. The skill guides algorithm analysis, complete code, performance optimization, and correctness checks through tests, assertions, or formal verification, meaning mathematical checks of correctness.

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

• Checking algorithm complexity and design assumptions
• Choosing languages for numerical or distributed systems
• Implementing concurrent code with explicit error handling

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

Explore an existing Vitest 3.2 JSON test report to count results, search failed tests, and inspect file errors. Review original diagnostic details and keep tentative explanations separate from evidence, without launching tests.

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

• Check failure counts in an existing test report
• Search failures by file path or diagnostic text
• Inspect file errors separately from failed assertions

Generate reusable test helpers for Godot, Unity, or Unreal projects. Create utilities for checking results, building test objects, and replacing dependencies, following the project's configured test framework and existing test patterns.

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

• Create a base library of test helpers
• Share repeated test setup and result checks
• Generate object factories for a specific game system

Review Handsontable code changes for architecture, code quality, performance, accessibility, and test coverage. Findings include severity, confidence, and file locations, helping developers assess whether changes follow project rules and demonstrate the intended behavior.

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

• Review a Handsontable branch or pull request
• Check architecture before or during core changes
• Review keyboard access and performance concerns

Create Playwright tests that capture table appearance and compare screenshots with reference images using reg-suit. The skill covers checking each state before capture, adding demo routes, and choosing themes, browsers, and framework variants to test.

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

• Checking table appearance after UI changes
• Adding screenshot tests for a new feature
• Comparing appearance across themes and browsers

Design and review TypeScript code with safer types and readable structures. Covers strict compiler settings, generics for reusable typed code, type guards for checking unknown values, and utility types for transforming existing definitions.

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

• Review TypeScript strict mode settings
• Design reusable functions with generics
• Replace unsafe assertions with type guards

Build runnable Foundry tests that demonstrate smart contract vulnerabilities with before-and-after logs and assertions. Use fork tests, which copy blockchain state, and test helpers to reproduce known DeFi incidents or prepare evidence for a report.

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

• Writing runnable proofs of concept for vulnerability reports
• Reproducing issues from a fixed blockchain block
• Controlling callers, time, and balances in tests

Verify development results before reporting success or preparing commits and pull requests. Run checks that support each claim, inspect their actual output, and report remaining gaps instead of relying on assumptions or another agent’s success message.

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

• Checking evidence before reporting a bug as fixed
• Confirming test and build results before a commit
• Verifying that a regression test detects the bug

Evaluate how well existing tests catch code changes, then combine the results with function relationships. Get a report separating harmless findings, missing unit tests, and targets for fuzzing, which tests many generated inputs.

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

• Triage code changes that existing tests failed to catch
• Prioritize missing unit tests
• Find functions suited to fuzzing

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

Launch the real iPolloWork app on Daytona or locally and run scripted end-to-end tests through its debugging connection. Collect machine-checkable assertions, validated screenshots, and reports as evidence of the tested behavior.

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

• Run scripted end-to-end tests on Daytona
• Collect screenshots and reports for a pull request
• Run tests locally when Daytona is unavailable

Upgrade MSTest v1 or v2 projects to v3, including partially completed migrations. Update packages, repair affected assertions and test data, replace legacy settings, and compare test results while preserving the existing test runner.

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

• Upgrading an MSTest v1 or v2 project to v3
• Fixing compilation errors after a v3 package update
• Repairing DataRow values that mismatch parameter types

Investigate MSBuild failures, measure slow builds, or review existing build definitions. Use binary logs, project settings, and comparable timing measurements to identify causes, propose focused repairs, and verify behavior without broad configuration changes.

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

• Investigating build failures from binary logs
• Measuring bottlenecks and comparing build times
• Finding why unchanged projects rebuild

Assess factual claims in AI-generated text by separating facts from opinions, choosing suitable independent evidence, and explaining what is supported or uncertain. Use it for a completed fact-check or an optional exercise in evaluating AI answers.

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

• Fact-checking an AI-generated answer
• Choosing independent sources for a claim
• Identifying unverified numbers and assertions

Investigate XXE, an XML parsing flaw, in APIs and document uploads. The skill guides entry point discovery, external callback checks, and evidence collection to establish whether files or internal services are actually exposed.

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

• Check XML APIs for external entity processing
• Investigate SVG and Office document uploads
• Confirm blind XXE through external callbacks