“test-driven”的搜索结果

将测试驱动开发用于功能新增和缺陷修复：先写测试并确认失败，再用最少代码使其通过，最后整理代码，逐项验证行为。

• 先写测试再添加功能
• 先复现缺陷再修复
• 保持测试通过并整理代码

Automatically repair source code against a failing test while preserving the test itself. Set a spending limit and attempt count, then receive verification results and usage costs based on rerunning the test command.

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

• Repairing a failing CI test after a commit
• Implementing code to pass a test written first
• Investigating a regression within a fixed budget

Follow Conductor's development plans using test-driven development: write a failing test, implement the change, then improve the code. Manage phase verification, progress updates, and focused git commits as tasks move toward completion.

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

• Implementing tasks from plan.md
• Following the test-driven development cycle
• Verifying completion at phase checkpoints

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

Create and improve agent skills by testing behavior before and after adding guidance. The skill applies test-driven development to SKILL.md documents, covering structure, discovery descriptions, supporting files, and checks that reveal unclear or ineffective instructions.

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

• Creating a reusable skill from a working method
• Testing an existing skill before deployment
• Improving descriptions so agents find relevant skills

Guides feature development and bug fixes through test-driven development: write a test, confirm the expected failure, then add the minimum code to pass. It also covers refactoring and checking the full test suite.

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

• Define expected behavior before building a feature
• Reproduce a bug with a failing test
• Refactor code while keeping tests passing

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

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

Test-driven development workflow with philosophy guide - plan → write tests → implement → validate

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

Test-driven development workflow with philosophy guide - plan → write tests → implement → validate

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

Use when Java implementation work should be guided by Test-Driven Development, including maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough production code to pass, and refactoring while keeping tests green. This should trigger for requests such as Apply TDD; Use test-driven development; Drive this Java change with tests; Write the failing test first; Red-green-refactor this feature. Part of Plinth Toolkit

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

Use only when the user explicitly invokes obra test-driven-development for iron-law examples. Core TDD is docs/ai/skills/tdd/SKILL.md. Do not use this for docs-only, formatting-only, or generated-mirror changes.

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

Test-Driven Development workflow for Software Metrics Machine. Covers test frameworks (Vitest 4.x for CLI/REST/core/utils, Jest 30.x for webapp), test patterns (describe/it, builder pattern, mocks via vi.fn), test commands, coverage requirements, and the Red-Green-Refactor cycle. USE FOR: write tests, run tests, test this, add tests, testing, coverage, TDD, test-driven development, vitest, jest, test pattern, test convention. DO NOT USE FOR: linting (use lint skill), building (use build commands directly), debugging production issues.

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

This skill should be used when developing code using Test-Driven Development (TDD) methodology. Use this skill when the user wants to write tests first before implementation, needs guidance on the red-green-refactor cycle, or explicitly requests TDD-style development. Triggers include requests like "develop this feature using TDD", "write tests first", "help me with test-driven development", or "implement this following TDD practices". The skill guides through writing failing tests, implementing minimal code to pass, and refactoring while maintaining test coverage.

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

Test-driven development: production-level red green refactor and boundaries. Use when implementing, reviewing or testing test-driven development for React, Vite, Next.js or Perfect_AI projects.

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

Implement test-driven development (TDD) workflow using the red-green-refactor cycle. Use when writing new features, fixing bugs, or refactoring existing code. Always write the failing test first, then implement minimal code to pass, then refactor. Essential for ensuring code reliability, preventing regressions, improving design through testability requirements, documenting expected behavior through tests, enabling confident refactoring, and maintaining high code quality standards throughout the development process.

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

Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.

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

通过先写测试、确认失败再实现的流程添加功能或修复缺陷。只编写让测试通过所需的代码，再保持测试通过并整理代码，完成前运行项目的完整测试集。

• 从测试开始实现新功能
• 用测试复现并修复缺陷
• 保持测试通过并重构代码

通过测试创建、修订和发布前验证 AI 智能体技能，比较使用指令前后的行为，找出遗漏或误解，并调整文档结构、搜索说明和措辞。

• 将重复流程整理成可复用技能
• 修订容易被误解的指令
• 在发布前验证技能

通过先写失败测试、再添加最小实现来开发功能或修复缺陷。从调用方使用的公开接口验证行为，编写不依赖内部结构的测试。

• 先写测试再添加功能
• 从缺陷复现测试开始修复
• 确定集成测试覆盖的接口

读取规格说明和相关工单的依赖关系，安排多个代理推进实现。经过测试、代码审查和问题修正后，将成果汇总到一个集成分支，并完成工单处理。

• 实现分散在多个工单中的需求
• 并行实现相互独立的任务
• 将成果汇总到集成分支

按测试驱动开发流程新增功能或修复缺陷：先确认测试按预期失败，再以最少代码使其通过，随后整理代码，并检查至少80%的测试覆盖率、记录验证结果。

• 从测试开始实现新功能
• 先复现缺陷再修复
• 保持测试通过并整理代码

通过先写测试的TDD流程，为Spring Boot添加功能、修复问题或整理代码，涵盖单元测试、Web层验证、数据持久化与集成测试，并检查代码覆盖率。

• 从测试开始添加Spring Boot API
• 编写防止问题复发的测试
• 验证数据保存与读取

通过先写测试，为Quarkus 3.x LTS服务添加功能、修复故障或重构，验证API、事件及异步处理，并检查测试覆盖率。

• 先写测试再添加REST API
• 复现并修复故障
• 验证Apache Camel路由和事件处理

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

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