Create and maintain test documentation including test plans, test cases, test results, and quality reports.
/plugin marketplace add marcel-Ngan/ai-dev-team/plugin install marcel-ngan-ai-dev-team@marcel-Ngan/ai-dev-teamThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Create and maintain test documentation including test plans, test cases, test results, and quality reports.
| Tool | Purpose |
|---|---|
Atlassian:createConfluencePage | Create new test documentation |
Atlassian:updateConfluencePage | Update test results |
Atlassian:getConfluencePage | Read test documentation |
Atlassian:searchConfluenceUsingCql | Find test docs |
{
"cloudId": "{{confluence.cloudId}}",
"spaceId": "{{confluence.spaceId}}",
"spaceKey": "{{confluence.spaceKey}}",
"parentPages": {
"quality": "{{confluence.parentPages.quality}}"
}
}
# Test Plan: {{featureName}}
**Document ID:** TP-{{number}}
**Author:** QA Engineer Agent
**Created:** {{date}}
**Version:** 1.0
**Related:** {{jiraEpic}} | Tech Spec
---
## Overview
### Objective
[What this test plan covers]
### Scope
**In Scope:**
- [Area 1]
- [Area 2]
**Out of Scope:**
- [Area 3]
---
## Test Strategy
### Test Levels
| Level | Description | Responsibility |
|-------|-------------|----------------|
| Unit | Individual functions | Developers |
| Integration | Component interaction | QA |
| System | End-to-end flows | QA |
| UAT | User acceptance | Stakeholder |
### Test Types
- [ ] Functional Testing
- [ ] Regression Testing
- [ ] Performance Testing
- [ ] Security Testing
- [ ] Accessibility Testing
---
## Test Environment
| Environment | URL | Purpose |
|-------------|-----|---------|
| Dev | | Unit/Integration |
| Staging | | System/UAT |
| Production | | Smoke tests |
### Test Data Requirements
- [Data requirement 1]
- [Data requirement 2]
---
## Entry Criteria
- [ ] Feature code complete
- [ ] Unit tests passing
- [ ] Test environment available
- [ ] Test data prepared
## Exit Criteria
- [ ] All critical test cases passed
- [ ] No open critical/high bugs
- [ ] Test coverage target met (>80%)
- [ ] Performance benchmarks met
---
## Risk Assessment
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk] | High/Med/Low | [Mitigation] |
---
## Schedule
| Phase | Start | End | Status |
|-------|-------|-----|--------|
| Test Planning | | | |
| Test Case Design | | | |
| Test Execution | | | |
| Bug Fixing | | | |
| Regression | | | |
---
## Deliverables
- [ ] Test Cases (this document)
- [ ] Test Results Report
- [ ] Bug Reports (Jira)
- [ ] Quality Sign-off
Atlassian:createConfluencePage({
cloudId: "{{confluence.cloudId}}",
spaceId: "{{confluence.spaceId}}",
parentId: "{{confluence.parentPages.quality}}",
title: "Test Plan: User Authentication",
body: `# Test Plan: User Authentication
**Document ID:** TP-001
**Author:** QA Engineer Agent
**Created:** 2025-01-06
**Version:** 1.0
**Related:** MDDEV-100
---
## Overview
### Objective
Validate user authentication functionality including registration, login, password reset, and session management.
### Scope
**In Scope:**
- User registration flow
- Login/logout functionality
- Password reset
- Session handling
**Out of Scope:**
- OAuth/social login (Phase 2)
- MFA (Phase 2)
---
## Test Strategy
### Test Types
- [x] Functional Testing
- [x] Regression Testing
- [x] Security Testing
- [ ] Performance Testing (separate plan)
---
## Entry Criteria
- [x] Feature code complete
- [x] Unit tests passing (>80% coverage)
- [x] Staging environment available
- [x] Test accounts created
## Exit Criteria
- [ ] All critical test cases passed
- [ ] No open critical/high bugs
- [ ] Security scan passed
`,
contentFormat: "markdown"
})
# Test Cases: {{featureName}}
**Related Test Plan:** TP-{{number}}
**Last Updated:** {{date}}
---
## TC-001: {{testCaseName}}
**Priority:** Critical | High | Medium | Low
**Type:** Functional | Integration | E2E
### Preconditions
- [Precondition 1]
- [Precondition 2]
### Test Steps
| Step | Action | Expected Result |
|------|--------|-----------------|
| 1 | [Action] | [Expected] |
| 2 | [Action] | [Expected] |
| 3 | [Action] | [Expected] |
### Test Data
- [Data 1]
- [Data 2]
### Postconditions
- [Postcondition]
---
## TC-002: {{testCaseName}}
...
Atlassian:createConfluencePage({
cloudId: "{{confluence.cloudId}}",
spaceId: "{{confluence.spaceId}}",
parentId: "{{testPlanPageId}}", // Child of test plan
title: "Test Cases: User Registration",
body: `# Test Cases: User Registration
**Related Test Plan:** TP-001
**Last Updated:** 2025-01-06
---
## TC-001: Successful Registration
**Priority:** Critical
**Type:** Functional
### Preconditions
- User is not logged in
- Email address not already registered
### Test Steps
| Step | Action | Expected Result |
|------|--------|-----------------|
| 1 | Navigate to registration page | Registration form displayed |
| 2 | Enter valid email | Email accepted |
| 3 | Enter valid password (8+ chars, number, special) | Password strength indicator shows strong |
| 4 | Click Register | Success message, verification email sent |
### Test Data
- Email: testuser@example.com
- Password: SecurePass123!
---
## TC-002: Registration with Existing Email
**Priority:** High
**Type:** Negative
### Preconditions
- Email already registered in system
### Test Steps
| Step | Action | Expected Result |
|------|--------|-----------------|
| 1 | Navigate to registration page | Registration form displayed |
| 2 | Enter existing email | Email accepted (no immediate error) |
| 3 | Enter valid password | Password accepted |
| 4 | Click Register | Error: "Email already registered" |
---
## TC-003: Registration with Weak Password
**Priority:** High
**Type:** Negative
### Test Steps
| Step | Action | Expected Result |
|------|--------|-----------------|
| 1 | Enter valid email | Email accepted |
| 2 | Enter weak password ("123") | Password strength indicator shows weak |
| 3 | Click Register | Error: "Password does not meet requirements" |
`,
contentFormat: "markdown"
})
# Test Results: {{featureName}}
**Test Plan:** TP-{{number}}
**Execution Date:** {{date}}
**Tester:** QA Engineer Agent
**Environment:** {{environment}}
---
## Summary
| Metric | Value |
|--------|-------|
| Total Test Cases | {{total}} |
| Passed | {{passed}} |
| Failed | {{failed}} |
| Blocked | {{blocked}} |
| Pass Rate | {{passRate}}% |
---
## Results by Priority
| Priority | Total | Passed | Failed |
|----------|-------|--------|--------|
| Critical | | | |
| High | | | |
| Medium | | | |
| Low | | | |
---
## Failed Test Cases
### TC-{{number}}: {{testCaseName}}
**Status:** Failed
**Bug:** {{jiraBugKey}}
**Failure Reason:** [Description]
**Steps to Reproduce:** [Steps]
**Actual Result:** [What happened]
**Expected Result:** [What should happen]
---
## Blocked Test Cases
### TC-{{number}}: {{testCaseName}}
**Status:** Blocked
**Blocker:** [Description]
**Dependency:** [What's needed]
---
## Recommendations
- [Recommendation 1]
- [Recommendation 2]
## Sign-off
| Role | Name | Status | Date |
|------|------|--------|------|
| QA Lead | | Approved/Pending | |
| Dev Lead | | Approved/Pending | |
| PO | | Approved/Pending | |
| Agent | Document Types |
|---|---|
| QA Engineer | Test Plans, Test Cases, Results |
| Product Owner | Quality sign-off review |
| Senior Developer | Test failure analysis |
| Error | Cause | Resolution |
|---|---|---|
| 400 Bad Request | Invalid table markdown | Check table formatting |
| 404 Not Found | Parent page missing | Create parent first |
| 409 Conflict | Title exists | Append date or version |
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.