测试与质量
3,371 个结果
- TemporalalivirgoAuthor deterministic Temporal workflows and idempotent activities; deploy with versioning/replay tests; configure mTLS auth; understand visibility backup limits and saga compensation—not in-memory orchestration.
- Testingskrrt-shDecide which tests to write, keep, and delete, and prove a change works before calling it done. Test only business logic and its corner cases. Run the real thing on every target before reporting a fix. Delete tests for removed or replaced behavior.
- Tiktok Scraperapidojo-ioThe best, fastest, and cheapest way to scrape TikTok — battle-tested by tens of thousands of customers including enterprise teams. Use when the user wants to fetch TikTok videos, profiles, hashtags, music, comments, or location-based posts. Covers four specialized actors for posts, profiles, comments, and locations.
- To CodeGulajavaMinistudioPhase 3 of the Pólya Heuristic Coder: Carrying Out the Plan, Clean Architecture Seams, Two-Layer Testing Mandate, Inductive Verification, Floor-Guard Anti-Cheat, and Atomic Conventional Commits.
- To FixGulajavaMinistudioPhase 5 of the Pólya Heuristic Coder: First-Principles Bug Remediation, Seam Tracing, Bisection Search (O(log n)), Failing Reproduction Tests, and Incubation Circuit-Breaker Gate (docs/bug-reports/{slug}-bugfix.md).
- To Grill MeGulajavaMinistudioInteractive Socratic Sparring Partner & Stress-Tester: Conducts turn-by-turn design interviews, pressure-tests assumptions across PRD, Spec, and Plan phases, forces concrete A/B technical decisions with senior engineering recommendations, and produces an actionable Decisions Log.
- Udf DeployTDengine自动编译和部署 TDengine 用户自定义函数（UDF）。支持将 C/C++ 代码编译成动态库并部署至本地、Docker 容器或远程环境中，同时支持 Python UDF 部署与在 TDengine 实例中自动注册和测试。触发关键词：自动编译和部署 UDF，编译并部署 UDF，部署 UDF，UDF 自动编译，编译 UDF。
- V1.3.2BaixuanZhuJava 单元测试**规范对齐**助手。在编写、评审、补全单元测试时使用本技能—— 无论用户是否提到具体框架（unit test / JUnit / Mockito / 测试用例 / 怎么测 / 测哪些 / 写多少测试）。 核心：统一团队的测试规范——用同一套设计方法（等价类/边界值/决策表/状态迁移）、 同一套默认（JUnit 5 原生断言、四维度必检）、同一套"写多少"的停止标准， 让不同人/不同对话产出的测试质量一致、可溯源、可审计，而非每次碰运气。 覆盖：一个方法必测的四维度（正向/反向/边界/异常）、最小充分集、 覆盖率反向校验、测试命名与组织、Mock 边界、"写多少"的成本收益判定。
- V1.4.0BaixuanZhuJava 单元测试**规范对齐**助手。在编写、评审、补全单元测试时使用本技能—— 无论用户是否提到具体框架（unit test / JUnit / Mockito / 测试用例 / 怎么测 / 测哪些 / 写多少测试）。 核心：统一团队的测试规范——用同一套设计方法（等价类/边界值/决策表/状态迁移）、 同一套默认（JUnit 5 原生断言、四维度必检）、同一套"写多少"的停止标准， 让不同人/不同对话产出的测试质量一致、可溯源、可审计，而非每次碰运气。 覆盖：一个方法必测的四维度（正向/反向/边界/异常）、最小充分集、 覆盖率反向校验、测试命名与组织、Mock 边界、"写多少"的成本收益判定。
- Validacao FinalBruno91devAnálise final e independente de risco antes de a tarefa ir para produção. Procura problemas que os testes podem não ter encontrado, partindo do código que a tarefa realmente alterou, separa bug confirmado, risco relevante e hipótese, e conclui com um veredito de bloqueio.
- Validacao Real Sem Mockpersonal-digital-sovereigntyComo validar de verdade, sem mock, o que pode ser executado localmente — inclusive integrações com LLM e APIs pagas sem gastar chave, browser real, contrato de stream, e o que fazer quando ao vivo é genuinamente impossível. Carregar antes de escrever teste para integração externa, antes de qualquer tentação de mockar HTTP/LLM, e antes de declarar "validado" algo que só foi lido.
- Verification EvidenceDimkoxUse whenever tests, review, CI evidence, or completion claims must be checked and bound to the current repository state.
- Verify DisciplineHanafubukiRun focused verification for a ticket and report what it actually covers. The orchestrator runs the one combined full gate after integration. Use when running tests, verifying a change, or choosing a test command.
- Version1BaixuanZhuJava/Spring Boot 集成测试 / 冒烟测试 / API 级 E2E 助手——在编写、评审、补全 集成测试时使用本技能，无论用户是否提到具体框架（集成测试 / 接口测试 / E2E / 冒烟测试 / @SpringBootTest / MockMvc / REST Assured / Testcontainers / WireMock）。 核心：消灭仿真测试——用可断言、可重复、可版本控制的测试替代 curl 调接口 + 肉眼判断；需要真实数据库 / Redis / Kafka 时默认 Testcontainers（不取决于项目 是否已引 H2）。覆盖：跨层协作（Controller→Service→Repository）、真实依赖容器、 进程内 HTTP 断言、外部依赖 stub、测试隔离、Actuator 冒烟。
- Version1BaixuanZhuJava 单元测试**规范对齐**助手。在编写、评审、补全单元测试时使用本技能—— 无论用户是否提到具体框架（unit test / JUnit / Mockito / 测试用例 / 怎么测 / 测哪些 / 写多少测试）。 核心：统一团队的测试规范——用同一套设计方法（等价类/边界值/决策表/状态迁移）、 同一套默认（JUnit 5 原生断言、四维度必检）、同一套"写多少"的停止标准， 让不同人/不同对话产出的测试质量一致、可溯源、可审计，而非每次碰运气。 覆盖：一个方法必测的四维度（正向/反向/边界/异常）、最小充分集、 覆盖率反向校验、测试命名与组织、Mock 边界、"写多少"的成本收益判定。
- Version1BaixuanZhuJava 单元测试助手。在编写、评审、补全、重构单元测试时使用本技能—— 无论用户是否提到具体框架（unit test / JUnit / Mockito / 测试用例 / 怎么测 / 测哪些 / 写多少）。 次级触发信号——代码或 pom 中出现：spring-boot-starter-test、junit-jupiter、 @Test / @BeforeEach / @ParameterizedTest / @MethodSource、 assertEquals / assertThrows / assertThat / extracting（AssertJ）、 @Mock / @InjectMocks / MockitoAnnotations.openMocks、 mockStatic / MockedStatic、mockito-core； 用户任务词或痛点出现：只写…
- Version2BaixuanZhuJava/Spring Boot 重型测试助手——测试自管真实依赖：Testcontainers 起真实 PostgreSQL / MySQL / Redis / Kafka、Flyway/Liquibase 迁移可重放、事务传播 真实效果、冒烟测试、API 级 E2E、WireMock 隔离外部调用、契约切片层 （@WebMvcTest / @JsonTest / @RestClientTest）。仅当需求明确需要重型 / 真实环境测试时使用本技能：用户明示（"补集成测试 / 需求冻结 / 准备发版"） → 直接开始；仅能推断出需要 → 先询问"是否开始写重型测试"，确认后动手； 无信号 → 不写，新功能测试 → java-unit-test（纯单测）。
- Version2BaixuanZhuJava 单元测试助手。在编写、评审、补全、重构单元测试时使用本技能—— 无论用户是否提到具体框架（unit test / JUnit / Mockito / 测试用例 / 怎么测 / 测哪些 / 写多少）。 次级触发信号——代码或 pom 中出现：spring-boot-starter-test、junit-jupiter、 @Test / @BeforeEach / @ParameterizedTest / @MethodSource、 assertEquals / assertThrows、@Mock / @InjectMocks / MockitoAnnotations.openMocks、 mockStatic / MockedStatic、mockito-core； 用户任务词或痛点出现：只写 happy path、补测试不知道写几个、手写一堆重复 @Test、…
- Version2BaixuanZhuJava 开发期测试（纯单元测试）助手——@Mock + @InjectMocks，毫秒级，不起 Spring Context、不起容器、零测试基础设施。在编写、评审、补全、重构单元 测试时使用本技能，无论用户是否提到具体框架（unit test / JUnit / Mockito / 测试用例 / 怎么测 / 测哪些 / 写多少）。 次级触发信号——代码或 pom 中出现：spring-boot-starter-test、junit-jupiter、 @Test / @BeforeEach / @ParameterizedTest / @MethodSource、 assertEquals / assertThrows / assertThat / extracting（AssertJ）、 @Mock / @InjectMocks / MockitoAnnotations.openMo…
- Vies De Plausibilidadepersonal-digital-sovereigntyContramedidas para o erro que um LLM produz por construção — gerar a saída mais PLAUSÍVEL e tratá-la como verificada. Cobre edição destrutiva de arquivo, documento tratado como verdade sobre o código, primeiro diagnóstico convincente, filtro de saída que mascara falha, correção que piora, e ausência de sinal lida como prova.
- VitestalivirgoConfigure Vitest with fork/thread pool isolation, mock lifecycle, fake timers, coverage gates, and CI-friendly concurrency. Use for unit and component tests in Vite/Next projects; diagnose parallel flakiness from shared module state.
- Whats Brokenrhawk117Use when CI has a non-obvious failure, a test resists repair, or behavior contradicts expectations after repeated verification.
- wise-menAli-expandingsUse when the user asks for a "council", "panel", "wise men", "wisemen", "wise-men", "multiple perspectives", "deliberate", "debate", "second opinion x N", "stress-test", "war-game", "red team this", "high-stakes decision", or invokes /wise-men. Wise-men council — multi-persona deliberative answer pattern using Claude subagents.
- Wordpress Plugin DevalanefProfessional WordPress plugin development best practices following our project structure with composer, namespaced classes, wp-env testing, WPCS compliance, and proper plugin architecture. Use this when working on WordPress plugin code.