“tests”的搜索结果

从测试开始实现 Laravel 功能，使用 PHPUnit 或 Pest 验证模型、API、身份认证和权限，模拟外部服务，并通过覆盖率了解测试执行了哪些代码。

• 从测试开始实现 Laravel 功能
• 验证 API 身份认证与权限
• 模拟支付、邮件和队列

为Kotlin代码先编写测试，使用Kotest和MockK验证行为与依赖交互，涵盖异步测试、生成输入的属性测试及Kover覆盖率检查。

• 为现有Kotlin代码补充测试
• 先写测试再开发新功能
• 验证协程和Flow的行为

协助编写和修复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

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 quality assurance tests on Holoscan Sensor Bridge hardware from a supplied test document. Select tests that match the connected equipment, execute automatable cases, evaluate pass or fail, and produce a structured results report.

中文简介正在准备中。当前显示英语简介。

• Run a documented test plan on an HSB board
• Select automated tests for the connected sensors
• Investigate failed tests using execution logs

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

中文简介正在准备中。当前显示原文说明。