comprehensive-testing-%26-verification by ananddtyagi/cc-marketplace
npx skills add https://github.com/ananddtyagi/cc-marketplace --skill 'Comprehensive Testing & Verification'在声称任何功能正常工作之前,必须遵循以下顺序:
// Test task creation
await page.click('[data-testid="quick-add-task"]')
await page.fill('[data-testid="task-title-input"]', 'Test Task')
await page.click('[data-testid="save-task"]')
await expect(page.locator('[data-testid="sidebar-task"]:has-text("Test Task")')).toBeVisible()
// Test calendar drag-drop
const sidebarTask = page.locator('[data-testid="sidebar-task"]').first()
const timeSlot = page.locator('[data-testid="time-slot"]').first()
await sidebarTask.dragTo(timeSlot)
await expect(page.locator('[data-testid="calendar-event"]')).toBeVisible()
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
在缺乏强制性测试证据的情况下,切勿声称功能正常工作。 每次成功声明都需要:
阶段 1:基线验证
npm run devnpm run build - 必须无错误通过阶段 2:更改实施
npm run build阶段 3:功能测试
阶段 4:跨视图验证
系统会自动检测您何时声明:
对于 UI 更改:
对于性能声明:
对于错误修复:
npm run dev 成功npm run build 无错误当系统检测到没有证据的成功声明时:
// Evidence Collection Template
const evidenceCollection = {
featureName: "Feature Name",
claimDate: new Date().toISOString(),
testingEnvironment: {
url: "http://localhost:5546",
browser: "chromium",
viewport: "1280x720"
},
tests: [
{
description: "Test specific functionality",
expectedResult: "Expected outcome",
actualResult: "Actual outcome",
status: "PASS/FAIL",
screenshot: "path/to/screenshot.png",
evidence: "Detailed test results"
}
],
verification: {
buildPassed: true,
consoleClean: true,
crossViewTested: true,
dataPersists: true,
noRegressions: true
}
}
这项全面的测试技能确保了对功能是否真正与真实数据一起工作、可验证的证据以及零容忍虚假成功声明的严格验证。所有声明在被接受之前都必须有强制性测试证据支持。
关键:在声称任何问题、错误或故障已"修复"、"解决"、"正常工作"或"完成"之前,以下验证协议是强制性的:
必需:使用 AskUserQuestion 工具明确要求用户验证修复:
"I've implemented [description of fix]. Before I mark this as complete, please verify:
1. [Specific thing to check #1]
2. [Specific thing to check #2]
3. Does this fix the issue you were experiencing?
Please confirm the fix works as expected, or let me know what's still not working."
请记住:用户是判断某事物是否已修复的最终权威。没有例外。
每周安装量
0
代码仓库
GitHub 星标数
657
首次出现
Jan 1, 1970
ALWAYS follow this sequence before claiming any feature works:
Environment Setup
Real Data Verification
Playwright MCP Testing
Cross-View Validation
// Test task creation
await page.click('[data-testid="quick-add-task"]')
await page.fill('[data-testid="task-title-input"]', 'Test Task')
await page.click('[data-testid="save-task"]')
await expect(page.locator('[data-testid="sidebar-task"]:has-text("Test Task")')).toBeVisible()
// Test calendar drag-drop
const sidebarTask = page.locator('[data-testid="sidebar-task"]').first()
const timeSlot = page.locator('[data-testid="time-slot"]').first()
await sidebarTask.dragTo(timeSlot)
await expect(page.locator('[data-testid="calendar-event"]')).toBeVisible()
NEVER claim functionality works without mandatory testing evidence. Every success declaration requires:
Phase 1: Baseline Verification
npm run devnpm run build - must pass without errorsPhase 2: Change Implementation
npm run build after every single changePhase 3: Functional Testing
Phase 4: Cross-View Verification
The system automatically detects when you claim:
For UI Changes:
For Performance Claims:
For Bug Fixes:
npm run dev succeedsnpm run build no errorsWhen the system detects a success claim without evidence:
// Evidence Collection Template
const evidenceCollection = {
featureName: "Feature Name",
claimDate: new Date().toISOString(),
testingEnvironment: {
url: "http://localhost:5546",
browser: "chromium",
viewport: "1280x720"
},
tests: [
{
description: "Test specific functionality",
expectedResult: "Expected outcome",
actualResult: "Actual outcome",
status: "PASS/FAIL",
screenshot: "path/to/screenshot.png",
evidence: "Detailed test results"
}
],
verification: {
buildPassed: true,
consoleClean: true,
crossViewTested: true,
dataPersists: true,
noRegressions: true
}
}
This comprehensive testing skill ensures rigorous validation that features actually work with real data, verifiable evidence, and zero tolerance for false success claims. All claims must be backed by mandatory testing evidence before being accepted.
CRITICAL : Before claiming ANY issue, bug, or problem is "fixed", "resolved", "working", or "complete", the following verification protocol is MANDATORY:
REQUIRED : Use the AskUserQuestion tool to explicitly ask the user to verify the fix:
"I've implemented [description of fix]. Before I mark this as complete, please verify:
1. [Specific thing to check #1]
2. [Specific thing to check #2]
3. Does this fix the issue you were experiencing?
Please confirm the fix works as expected, or let me know what's still not working."
Remember: The user is the final authority on whether something is fixed. No exceptions.
Weekly Installs
0
Repository
GitHub Stars
657
First Seen
Jan 1, 1970
Skills CLI 使用指南:AI Agent 技能包管理器安装与管理教程
31,600 周安装