'parameterized' 검색 결과

Provides parameterized testing patterns with JUnit 5, generates data-driven unit tests using @ParameterizedTest, @ValueSource, @CsvSource, @MethodSource. Creates tests that run the same logic with multiple input values. Use when writing data-driven Java tests, multiple test cases from single method, or boundary value analysis.

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

Create parameterized Quarto or R Markdown reports that can be rendered with different inputs to generate multiple variations. Covers parameter definitions, programmatic rendering, and batch generation. Use when generating the same report for different departments, regions, or time periods; creating client-specific reports from a single template; building dashboards that filter to specific subsets; or automating recurring reports with varying inputs.

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

Perl 코드의 입력 처리, 파일 작업, 외부 명령, SQL과 웹 출력을 점검합니다. 구체적인 예시와 점검표에 따라 안전한 구현으로 수정합니다.

• Perl 입력 검증을 점검합니다
• 파일 작업과 명령 실행을 확인합니다
• DBI의 SQL 삽입 공격에 대비합니다

Create or improve unit tests for Apache ShardingSphere classes. Cover the target class’s behavior and affected branches, verify explicitly requested coverage goals, and consolidate suitable scenarios into parameterized tests, which run the same checks with different inputs.

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

• Add missing unit tests for a target class
• Verify an explicitly requested coverage target
• Consolidate suitable tests with different input data

Analyze .NET test suites for repeated setup, assertions, and copied test methods. Get a report with file locations, before-and-after refactoring examples, priorities, and readability trade-offs, without changing the source files.

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

• Finding repeated setup and assertions
• Combining copied tests into parameterized tests
• Identifying shared setup and cleanup opportunities

Use when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests, @ParameterizedTest with @CsvSource / @MethodSource, QuarkusTestProfile for test-specific configuration overrides, and naming conventions (*Test → Surefire, *IT → Failsafe). For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Quarkus project; Reduce slow @QuarkusTest usage with Mockito-first tests; Add @InjectSpy partial mocking or QuarkusTestProfile configuration in Quarkus tests; Convert repeated test methods to @ParameterizedTest with @CsvSource or @MethodSource; Write fast pure unit tests for Quarkus services. Part of Plinth Toolkit

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

Entity Framework Core patterns for ASP.NET Core projects: DbContext design, code-first entity configuration (Fluent API via IEntityTypeConfiguration<T>), relations (HasOne/HasMany, cascade/restrict/set-null), indexes and unique constraints, projection to DTOs (Select + AsNoTracking), avoiding N+1 (Include, AsSplitQuery), transactions, parameterized raw SQL (FromSql with FormattableString), and connection string from IConfiguration. Works alongside aspnet-core-plugin:aspnet-conventions. Use this skill to: - Design a clean DbContext with ApplyConfigurationsFromAssembly for scalable entity registration. - Configure entity properties (column types, max length, precision, nullability) via Fluent API. - Avoid N+1 query problems with explicit Include / projection to DTOs. - Use transactions correctly for multi-entity operations. - Write parameterized raw SQL safely when LINQ is not expressive enough. Do NOT use this skill for: - Migration generation commands (that is efcore-specialist's job in the database extra phase). - ASP.NET Core middleware, DI, or validation — see aspnet-core-plugin:aspnet-conventions. - C# language idioms — see csharp-foundation:csharp-conventions.

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

Write and migrate tests using the Swift Testing framework with @Test, @Suite, #expect, #require, confirmation, parameterized tests, test tags, traits, withKnownIssue, XCTest UI testing, XCUITest, test plan, mocking, test doubles, testable architecture, snapshot testing, async test patterns, test organization, and test-driven development in Swift. Use when writing or migrating tests with Swift Testing framework, implementing parameterized tests, working with test traits, converting XCTest to Swift Testing, or setting up test organization and mocking patterns.

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

Complete guide for AutoFixture and xUnit integration. Use when you need to use AutoData or InlineAutoData to simplify xUnit parameterized test data preparation. Covers custom Customization and test data attributes to improve test readability and maintainability. Keywords: AutoData, InlineAutoData, AutoFixture xUnit, [AutoData], [InlineAutoData], AutoDataAttribute, ICustomization, DataAttribute, parameterized test, Theory AutoData, MemberAutoData, test data attributes, fixture.Customize

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

Quarkus 앱의 인증, 접근 권한, 입력 검증을 구현하고 점검합니다. 비밀 정보 관리, 비밀번호 해싱, 요청 제한, 감사 로그와 의존성의 알려진 취약점도 다룹니다.

• Quarkus API에 JWT 또는 OIDC 인증 추가
• 역할별 권한과 데이터 소유자 확인 점검
• 입력 검증과 데이터베이스 조회 검토

Add a live adjustment panel to an HTML page so viewers can explore colors, text sizes, spacing, themes, and motion. Changes appear immediately and are saved in the browser for the next visit.

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

• Fine-tune a landing page’s colors and spacing
• Demonstrate brand or design system variations
• Add adjustable appearance controls to a standalone demo

Turn recurring GUI workflows into macros that agents can call from the command line with parameters. Define and inspect macros, simulate runs before making changes, and review structured results and execution history.

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

• Repeat export tasks with different output paths
• Check macro parameters before making changes
• Create a YAML macro for a recurring workflow

Build Python code for Azure Cosmos DB's NoSQL API to create, read, update, delete, and query documents. Covers authentication, containers for storing data, partition keys for distributing records, throughput settings, asynchronous operations, and error handling.

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

• Implementing document operations in Python
• Writing parameterized queries for filtered searches
• Configuring containers, partition keys, and throughput

Extract figures and fields from emails, websites, and APIs into source-linked tracking tables. Configurable recipes guide collection, preserve original material, and check duplicates for records such as investor updates, expenses, and company metrics.

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

• Track financial metrics from investor update emails
• Collect expenses from receipt emails
• Maintain a table of company updates

Implement application security controls, including login, access permissions, password hashing, and input validation. The skill provides code, configuration requirements, and testing guidance for checking protections against unauthorized access, malicious input, and sensitive data exposure.

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

• Implementing login with password hashing and rate limits
• Adding JWT validation and session protection
• Preventing SQL injection and malicious script execution

Build web application features across the interface, API, and database, with authentication, input checks, and safe data handling. The skill guides technical design, implementation, error handling, and component testing in one workflow.

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

• Building data entry and editing forms with matching APIs
• Adding authenticated profile pages
• Designing data flows from database to interface

Convert NUnit 3 or 4 tests to MSTest v4 while keeping the existing target framework and test runner. The workflow translates assertions, test data, setup, and concurrency settings, then compares test counts and results.

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

• Migrating NUnit 3 or 4 tests to MSTest v4
• Preserving parameterized tests and test data
• Reviewing shared state and parallel execution during migration

Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite; for database testing; or for questions about database/sql, sqlx, or pgx. Does NOT generate database schemas or migration SQL.

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

Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers on phrases like "Cosmos DB", "NoSQL database", "document store", "add persistence", "database service layer", or "Python Cosmos SDK".

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

Migrate RestTemplate to RestClient in Spring Boot 3.2+. Use when replacing deprecated RestTemplate with modern fluent API, updating HTTP client code, or configuring RestClient beans. Covers GET/POST/DELETE migrations, error handling, and ParameterizedTypeReference usage.

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

Scaffold and run a reproducible Monte Carlo simulation study in R — a declared assumption regime, a parameterized DGP, an estimator grid, a seeded replication loop, and a summary of bias, RMSE, empirical SE, coverage, size/power with Monte Carlo standard errors. Use when the user says "run a Monte Carlo simulation", "simulation study", "check the bias/coverage of an estimator", "compare estimators in simulation", "size and power simulation", "Monte Carlo experiment", or wants to demonstrate an estimator's finite-sample properties. Produces a numbered R script in `scripts/R/` and saves per-replication raw results + a summary table to `output/`.

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

Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or similar.

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

Gates whether a new test should exist and forces it to be efficient, protecting CI from low-value test bloat. Use before any change to what a pytest, Jest, or Playwright test asserts or sets up, down to one fixture or one assertion added to an existing block. Front-loads the value bar (every test must catch a realistic regression no existing test already catches; extend the nearest existing test before writing a new standalone one; test behavior through the public interface, not implementation details; collapse near-duplicates into parameterized cases) and the efficiency bar (deterministic, isolated, fast; pick the cheapest test level; Django TestCase over TransactionTestCase; no sleeps, no real network; no time bombs from absolute dates left to age against the real clock; no database a test never uses). Includes a "don't write it" decision tree. For fixing an existing flaky test use `/fixing-flaky-tests`; after this gate says a Playwright test is warranted, use `/playwright-test` for mechanics.

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

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.

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