[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70H4RM9QR3SV3820AJCT536":3,"skill-same:01M70H4RM9QR3SV3820AJCT536":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M70H4RM9QR3SV3820AJCT536","exploratory-testing",null,"Test charter structure, SFDPOT and FEW HICCUPPS heuristics, edge case discovery patterns, and session-based test management. Use when conducting exploratory testing, discovering edge cases, validating user journeys, or finding issues automated tests miss.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fquality\u002Fexploratory-testing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"testing","exploratory testing","user","management","charter","test","case","use","test management","edge","tests","session","discovery","patterns","structure","when","issues","heuristics","user journeys","2026-11-10 10:12:30",false,"---\nname: exploratory-testing\ndescription: Test charter structure, SFDPOT and FEW HICCUPPS heuristics, edge case discovery patterns, and session-based test management. Use when conducting exploratory testing, discovering edge cases, validating user journeys, or finding issues automated tests miss.\n---\n\n# Exploratory Testing Heuristics\n\nSystematic heuristics and techniques for discovering defects through creative exploration that complements automated testing.\n\n## When to Activate\n\n- Testing new features manually\n- Discovering edge cases and boundary conditions\n- Validating user journeys end-to-end\n- Finding issues automated tests miss\n- Evaluating usability and user experience\n- Security probing and input validation testing\n\n## Test Charters\n\nA charter provides focus and structure for exploration.\n\n### Charter Template\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ CHARTER: [Short descriptive title]                          │\n├─────────────────────────────────────────────────────────────┤\n│ TARGET:                                                      │\n│ [Feature, component, or area under test]                    │\n│                                                             │\n│ DURATION:                                                    │\n│ [Time box: 30, 60, 90 minutes]                              │\n│                                                             │\n│ MISSION:                                                     │\n│ Explore [target]                                            │\n│ With [resources, techniques, data]                          │\n│ To discover [types of issues, risks]                        │\n├─────────────────────────────────────────────────────────────┤\n│ SESSION NOTES:                                               │\n│ - [Timestamp] [Observation]                                 │\n│ - [Timestamp] [Bug found]                                   │\n│ - [Timestamp] [Question raised]                             │\n├─────────────────────────────────────────────────────────────┤\n│ BUGS FOUND:                                                  │\n│ [ ] BUG-001: [Title]                                        │\n│ [ ] BUG-002: [Title]                                        │\n├─────────────────────────────────────────────────────────────┤\n│ QUESTIONS\u002FCONCERNS:                                          │\n│ - [Question needing clarification]                          │\n│                                                             │\n│ COVERAGE NOTES:                                              │\n│ - Tested: [What was covered]                                │\n│ - Not tested: [What remains]                                │\n└─────────────────────────────────────────────────────────────┘\n```\n\n### Example Charters\n\n```\nCHARTER: Checkout Edge Cases\nTARGET: Shopping cart and checkout flow\nDURATION: 60 minutes\nMISSION:\n  Explore checkout with unusual cart combinations\n  With empty carts, single items, max items, mixed currencies\n  To discover payment failures and data integrity issues\n\n---\n\nCHARTER: Mobile Login Stress\nTARGET: Authentication on mobile devices\nDURATION: 45 minutes\nMISSION:\n  Explore login\u002Flogout under poor network conditions\n  With airplane mode, 2G simulation, wifi switching\n  To discover session handling and offline behavior issues\n\n---\n\nCHARTER: Search Manipulation\nTARGET: Product search functionality\nDURATION: 30 minutes\nMISSION:\n  Explore search with special characters and edge inputs\n  With SQL injection, XSS payloads, Unicode, emojis\n  To discover security vulnerabilities and input handling issues\n```\n\n## SFDPOT Heuristic\n\nA mnemonic for comprehensive coverage across six dimensions.\n\n### The Framework\n\n| Letter | Dimension | Focus |\n|--------|-----------|-------|\n| **S** | Structure | Data and code organization |\n| **F** | Function | What the product does |\n| **D** | Data | Information flowing through |\n| **P** | Platform | Environment dependencies |\n| **O** | Operations | How it's used in practice |\n| **T** | Time | Temporal aspects |\n\n### Detailed Questions\n\n#### S - Structure\n\n```\nQuestions:\n- What are the components and how do they connect?\n- What does the database schema look like?\n- What are the file\u002Ffolder structures?\n- What configuration options exist?\n- What are the integration points?\n\nExploration:\n- Map the system architecture\n- Trace data through components\n- Test component isolation\n- Verify configuration handling\n```\n\n#### F - Function\n\n```\nQuestions:\n- What are all the features?\n- What are the inputs and outputs?\n- What transformations occur?\n- What are the business rules?\n- What calculations are performed?\n\nExploration:\n- Test each feature systematically\n- Verify all stated functionality\n- Check feature interactions\n- Validate business logic\n```\n\n#### D - Data\n\n```\nQuestions:\n- What data types are handled?\n- What are the valid ranges?\n- How is data validated?\n- How is data stored and retrieved?\n- What happens with invalid data?\n\nExploration:\n- Boundary value testing\n- Invalid input testing\n- Data type mismatches\n- Empty\u002Fnull\u002Fmissing data\n- Large data volumes\n```\n\n#### P - Platform\n\n```\nQuestions:\n- What operating systems?\n- What browsers and versions?\n- What devices and screen sizes?\n- What network conditions?\n- What dependencies exist?\n\nExploration:\n- Cross-browser testing\n- Mobile device testing\n- Different OS versions\n- Network throttling\n- Dependency version testing\n```\n\n#### O - Operations\n\n```\nQuestions:\n- How is it installed\u002Fdeployed?\n- How is it configured?\n- How is it maintained?\n- How is it monitored?\n- How is it backed up?\n\nExploration:\n- Installation procedures\n- Upgrade\u002Fdowngrade paths\n- Backup and recovery\n- Configuration changes\n- Log and monitoring verification\n```\n\n#### T - Time\n\n```\nQuestions:\n- What happens over time?\n- Are there timeouts?\n- What about scheduling?\n- How does concurrency work?\n- What about time zones?\n\nExploration:\n- Long-running sessions\n- Timeout behaviors\n- Scheduled tasks\n- Race conditions\n- Time zone handling\n- Daylight saving transitions\n```\n\n## FEW HICCUPPS Heuristic\n\nConsistency oracles for judging whether behavior is correct.\n\n### The Framework\n\nEach letter represents a source of expectations:\n\n| Letter | Oracle | Question |\n|--------|--------|----------|\n| **F** | Familiarity | Is it consistent with similar products? |\n| **E** | Explainability | Can we explain this behavior to users? |\n| **W** | World | Is it consistent with the real world? |\n| **H** | History | Is it consistent with past versions? |\n| **I** | Image | Is it consistent with the brand\u002Freputation? |\n| **C** | Comparable | Is it consistent with competitors? |\n| **C** | Claims | Is it consistent with documentation? |\n| **U** | Users | Is it consistent with user expectations? |\n| **P** | Purpose | Is it consistent with stated goals? |\n| **P** | Product | Is it internally consistent? |\n| **S** | Statutes | Is it consistent with regulations? |\n\n### Using the Oracles\n\n```\nFor each observed behavior, ask:\n\nFAMILIARITY\n\"I've used similar products. This feels wrong because...\"\n\nEXPLAINABILITY\n\"If a user asked why it works this way, I couldn't explain because...\"\n\nWORLD\n\"In the real world, this doesn't make sense because...\"\n\nHISTORY\n\"The previous version didn't work this way. The change seems...\"\n\nIMAGE\n\"This doesn't match what I'd expect from a quality product because...\"\n\nCOMPARABLE\n\"Competitor X handles this by... Our approach seems...\"\n\nCLAIMS\n\"The documentation says X, but the behavior is Y...\"\n\nUSERS\n\"Users would expect... but instead they get...\"\n\nPURPOSE\n\"The stated goal is X, but this feature undermines it by...\"\n\nPRODUCT\n\"This part works like X, but that part works like Y. Inconsistent...\"\n\nSTATUTES\n\"This might violate [regulation\u002Flaw] because...\"\n```\n\n## Edge Case Patterns\n\n### Boundary Value Testing\n\n```\nINPUT BOUNDARIES:\n\nFor numeric inputs:\n┌────────────────────────────────────────────────┐\n│ Value  │ Type                                  │\n├────────────────────────────────────────────────┤\n│ -1     │ Below minimum                         │\n│ 0      │ Minimum boundary                      │\n│ 1      │ Just above minimum                    │\n│ ...    │ Typical values                        │\n│ max-1  │ Just below maximum                    │\n│ max    │ Maximum boundary                      │\n│ max+1  │ Above maximum                         │\n└────────────────────────────────────────────────┘\n\nFor string inputs:\n- Empty string: \"\"\n- Single character: \"a\"\n- Maximum length\n- Maximum length + 1\n- Only whitespace: \"   \"\n- Leading\u002Ftrailing whitespace: \" test \"\n```\n\n### Special Input Values\n\n```\nEMPTY\u002FNULL\u002FMISSING:\n- null\n- undefined\n- Empty string \"\"\n- Empty array []\n- Empty object {}\n- Whitespace only\n- Missing required fields\n\nNUMERIC EDGE CASES:\n- 0, -0\n- Negative numbers\n- Decimals (0.1, 0.01)\n- Scientific notation (1e10)\n- MAX_INT, MIN_INT\n- MAX_INT + 1 (overflow)\n- Infinity, -Infinity\n- NaN\n\nSTRING EDGE CASES:\n- Unicode: \"Ṁöñᵗý Ṗẏẗḧöñ\"\n- Emojis: \"😀🎉🔥\"\n- RTL text: \"مرحبا\"\n- Null byte: \"test\\x00injection\"\n- Very long strings (10KB+)\n- Format strings: \"%s %n %d\"\n- Path traversal: \"..\u002F..\u002F..\u002Fetc\u002Fpasswd\"\n\nDATE\u002FTIME EDGE CASES:\n- Leap years (Feb 29)\n- Daylight saving transitions\n- End of month (Jan 31 → Feb 28)\n- End of year (Dec 31 → Jan 1)\n- Time zone boundaries\n- Unix epoch (1970-01-01)\n- Y2K-style dates (2038 problem)\n- Far future dates\n```\n\n### State Transition Testing\n\n```\nTest all valid transitions AND invalid ones:\n\nORDER STATUS:\n┌────────┐    ┌───────────┐    ┌────────┐\n│ Draft  │───►│ Confirmed │───►│Shipped │\n└────────┘    └───────────┘    └────────┘\n     │              │              │\n     ▼              ▼              ▼\n┌────────┐    ┌───────────┐    ┌────────┐\n│Cancelled│   │ Cancelled │    │Delivered│\n└────────┘    └───────────┘    └────────┘\n\nTest:\n✓ Valid: Draft → Confirmed → Shipped → Delivered\n✓ Valid: Confirmed → Cancelled\n✗ Invalid: Shipped → Draft (should fail)\n✗ Invalid: Delivered → Confirmed (should fail)\n```\n\n### Error Condition Testing\n\n```\nNETWORK ERRORS:\n- Connection timeout\n- Connection refused\n- DNS failure\n- SSL certificate errors\n- Partial response\n- Corrupted response\n\nRESOURCE ERRORS:\n- Disk full\n- Out of memory\n- Too many open files\n- Permission denied\n- File locked\n\nCONCURRENCY ERRORS:\n- Race conditions\n- Deadlocks\n- Lost updates\n- Double submissions\n```\n\n## Session-Based Test Management\n\n### Session Metrics\n\n```\nSESSION REPORT:\n┌─────────────────────────────────────────────────────────────┐\n│ Tester: [Name]                                              │\n│ Charter: [Title]                                            │\n│ Date: [Date]           Duration: [Actual time]              │\n├─────────────────────────────────────────────────────────────┤\n│ TIME BREAKDOWN:                                              │\n│ ┌────────────────────────────────────────────────────────┐ │\n│ │ Testing:        ████████████████████ 60%              │ │\n│ │ Bug Investigation: ██████████ 25%                      │ │\n│ │ Setup\u002FOverhead:    █████ 15%                           │ │\n│ └────────────────────────────────────────────────────────┘ │\n├─────────────────────────────────────────────────────────────┤\n│ OUTCOMES:                                                    │\n│ Bugs filed: [count]                                         │\n│ Questions raised: [count]                                   │\n│ Test ideas generated: [count]                               │\n│ Coverage areas: [list]                                      │\n├─────────────────────────────────────────────────────────────┤\n│ FOLLOW-UP:                                                   │\n│ - [Next charter suggestion]                                 │\n│ - [Area needing more coverage]                              │\n└─────────────────────────────────────────────────────────────┘\n```\n\n### Coverage Visualization\n\n```\nFEATURE COVERAGE MAP:\n\nFeature                Testing Coverage\n─────────────────────────────────────────\nLogin                  ████████████████ 100%\nRegistration           ████████████░░░░  75%\nSearch                 ████████░░░░░░░░  50%\nCheckout               ████████████████ 100%\nProfile                ████░░░░░░░░░░░░  25%\nAdmin                  ░░░░░░░░░░░░░░░░   0%\n\nLegend: █ Tested  ░ Not tested\n```\n\n## Bug Reporting\n\n### Bug Report Template\n\n```markdown\n# BUG-[ID]: [Descriptive Title]\n\n## Summary\n[One sentence description]\n\n## Environment\n- Browser\u002FDevice: [e.g., Chrome 120 on macOS]\n- URL: [where it occurred]\n- User: [role\u002Faccount type]\n\n## Steps to Reproduce\n1. [First step]\n2. [Second step]\n3. [Third step]\n\n## Expected Result\n[What should happen]\n\n## Actual Result\n[What actually happened]\n\n## Evidence\n- Screenshot: [attached]\n- Video: [link]\n- Console log: [attached]\n\n## Severity\n[Critical \u002F High \u002F Medium \u002F Low]\n\n## Notes\n[Additional context, related issues, workarounds]\n```\n\n### Severity Guidelines\n\n| Level | Definition | Example |\n|-------|------------|---------|\n| **Critical** | System unusable, data loss | Payment double-charging |\n| **High** | Major feature broken | Cannot complete checkout |\n| **Medium** | Feature impaired, workaround exists | Search requires exact match |\n| **Low** | Minor issue, cosmetic | Alignment off by 2px |\n\n## Best Practices\n\n### Do\n\n- **Time-box sessions** - 60-90 minutes max before break\n- **Take notes continuously** - Capture observations as you go\n- **Follow your curiosity** - Interesting behavior often hides bugs\n- **Vary your approach** - Don't test the same way every time\n- **Question everything** - \"Is this right?\" should be constant\n- **Document coverage** - Know what you've tested and what remains\n\n### Avoid\n\n- **Random clicking** - Exploration should be purposeful\n- **Only happy paths** - Edge cases hide the interesting bugs\n- **Ignoring instincts** - \"That's weird\" often leads to bugs\n- **Testing in isolation** - Consider the full user journey\n- **Rushing** - Quality exploration takes focused time\n\n## References\n\n- [Charter Templates](examples\u002Fcharters.md) - Ready-to-use charter templates\n- [Heuristic Quick Reference](reference.md) - Printable heuristic cards\n","# Exploratory Testing Heuristics\n\nSystematic heuristics and techniques for discovering defects through creative exploration that complements automated testing.\n\n## When to Activate\n\n- Testing new features manually\n- Discovering edge cases and boundary conditions\n- Validating user journeys end-to-end\n- Finding issues automated tests miss\n- Evaluating usability and user experience\n- Security probing and input validation testing\n\n## Test Charters\n\nA charter provides focus and structure for exploration.\n\n### Charter Template\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ CHARTER: [Short descriptive title]                          │\n├─────────────────────────────────────────────────────────────┤\n│ TARGET:                                                      │\n│ [Feature, component, or area under test]                    │\n│                                                             │\n│ DURATION:                                                    │\n│ [Time box: 30, 60, 90 minutes]                              │\n│                                                             │\n│ MISSION:                                                     │\n│ Explore [target]                                            │\n│ With [resources, techniques, data]                          │\n│ To discover [types of issues, risks]                        │\n├─────────────────────────────────────────────────────────────┤\n│ SESSION NOTES:                                               │\n│ - [Timestamp] [Observation]                                 │\n│ - [Timestamp] [Bug found]                                   │\n│ - [Timestamp] [Question raised]                             │\n├─────────────────────────────────────────────────────────────┤\n│ BUGS FOUND:                                                  │\n│ [ ] BUG-001: [Title]                                        │\n│ [ ] BUG-002: [Title]                                        │\n├─────────────────────────────────────────────────────────────┤\n│ QUESTIONS\u002FCONCERNS:                                          │\n│ - [Question needing clarification]                          │\n│                                                             │\n│ COVERAGE NOTES:                                              │\n│ - Tested: [What was covered]                                │\n│ - Not tested: [What remains]                                │\n└─────────────────────────────────────────────────────────────┘\n```\n\n### Example Charters\n\n```\nCHARTER: Checkout Edge Cases\nTARGET: Shopping cart and checkout flow\nDURATION: 60 minutes\nMISSION:\n  Explore checkout with unusual cart combinations\n  With empty carts, single items, max items, mixed currencies\n  To discover payment failures and data integrity issues\n\n---\n\nCHARTER: Mobile Login Stress\nTARGET: Authentication on mobile devices\nDURATION: 45 minutes\nMISSION:\n  Explore login\u002Flogout under poor network conditions\n  With airplane mode, 2G simulation, wifi switching\n  To discover session handling and offline behavior issues\n\n---\n\nCHARTER: Search Manipulation\nTARGET: Product search functionality\nDURATION: 30 minutes\nMISSION:\n  Explore search with special characters and edge inputs\n  With SQL injection, XSS payloads, Unicode, emojis\n  To discover security vulnerabilities and input handling issues\n```\n\n## SFDPOT Heuristic\n\nA mnemonic for comprehensive coverage across six dimensions.\n\n### The Framework\n\n| Letter | Dimension | Focus |\n|--------|-----------|-------|\n| **S** | Structure | Data and code organization |\n| **F** | Function | What the product does |\n| **D** | Data | Information flowing through |\n| **P** | Platform | Environment dependencies |\n| **O** | Operations | How it's used in practice |\n| **T** | Time | Temporal aspects |\n\n### Detailed Questions\n\n#### S - Structure\n\n```\nQuestions:\n- What are the components and how do they connect?\n- What does the database schema look like?\n- What are the file\u002Ffolder structures?\n- What configuration options exist?\n- What are the integration points?\n\nExploration:\n- Map the system architecture\n- Trace data through components\n- Test component isolation\n- Verify configuration handling\n```\n\n#### F - Function\n\n```\nQuestions:\n- What are all the features?\n- What are the inputs and outputs?\n- What transformations occur?\n- What are the business rules?\n- What calculations are performed?\n\nExploration:\n- Test each feature systematically\n- Verify all stated functionality\n- Check feature interactions\n- Validate business logic\n```\n\n#### D - Data\n\n```\nQuestions:\n- What data types are handled?\n- What are the valid ranges?\n- How is data validated?\n- How is data stored and retrieved?\n- What happens with invalid data?\n\nExploration:\n- Boundary value testing\n- Invalid input testing\n- Data type mismatches\n- Empty\u002Fnull\u002Fmissing data\n- Large data volumes\n```\n\n#### P - Platform\n\n```\nQuestions:\n- What operating systems?\n- What browsers and versions?\n- What devices and screen sizes?\n- What network conditions?\n- What dependencies exist?\n\nExploration:\n- Cross-browser testing\n- Mobile device testing\n- Different OS versions\n- Network throttling\n- Dependency version testing\n```\n\n#### O - Operations\n\n```\nQuestions:\n- How is it installed\u002Fdeployed?\n- How is it configured?\n- How is it maintained?\n- How is it monitored?\n- How is it backed up?\n\nExploration:\n- Installation procedures\n- Upgrade\u002Fdowngrade paths\n- Backup and recovery\n- Configuration changes\n- Log and monitoring verification\n```\n\n#### T - Time\n\n```\nQuestions:\n- What happens over time?\n- Are there timeouts?\n- What about scheduling?\n- How does concurrency work?\n- What about time zones?\n\nExploration:\n- Long-running sessions\n- Timeout behaviors\n- Scheduled tasks\n- Race conditions\n- Time zone handling\n- Daylight saving transitions\n```\n\n## FEW HICCUPPS Heuristic\n\nConsistency oracles for judging whether behavior is correct.\n\n### The Framework\n\nEach letter represents a source of expectations:\n\n| Letter | Oracle | Question |\n|--------|--------|----------|\n| **F** | Familiarity | Is it consistent with similar products? |\n| **E** | Explainability | Can we explain this behavior to users? |\n| **W** | World | Is it consistent with the real world? |\n| **H** | History | Is it consistent with past versions? |\n| **I** | Image | Is it consistent with the brand\u002Freputation? |\n| **C** | Comparable | Is it consistent with competitors? |\n| **C** | Claims | Is it consistent with documentation? |\n| **U** | Users | Is it consistent with user expectations? |\n| **P** | Purpose | Is it consistent with stated goals? |\n| **P** | Product | Is it internally consistent? |\n| **S** | Statutes | Is it consistent with regulations? |\n\n### Using the Oracles\n\n```\nFor each observed behavior, ask:\n\nFAMILIARITY\n\"I've used similar products. This feels wrong because...\"\n\nEXPLAINABILITY\n\"If a user asked why it works this way, I couldn't explain because...\"\n\nWORLD\n\"In the real world, this doesn't make sense because...\"\n\nHISTORY\n\"The previous version didn't work this way. The change seems...\"\n\nIMAGE\n\"This doesn't match what I'd expect from a quality product because...\"\n\nCOMPARABLE\n\"Competitor X handles this by... Our approach seems...\"\n\nCLAIMS\n\"The documentation says X, but the behavior is Y...\"\n\nUSERS\n\"Users would expect... but instead they get...\"\n\nPURPOSE\n\"The stated goal is X, but this feature undermines it by...\"\n\nPRODUCT\n\"This part works like X, but that part works like Y. Inconsistent...\"\n\nSTATUTES\n\"This might violate [regulation\u002Flaw] because...\"\n```\n\n## Edge Case Patterns\n\n### Boundary Value Testing\n\n```\nINPUT BOUNDARIES:\n\nFor numeric inputs:\n┌────────────────────────────────────────────────┐\n│ Value  │ Type                                  │\n├────────────────────────────────────────────────┤\n│ -1     │ Below minimum                         │\n│ 0      │ Minimum boundary                      │\n│ 1      │ Just above minimum                    │\n│ ...    │ Typical values                        │\n│ max-1  │ Just below maximum                    │\n│ max    │ Maximum boundary                      │\n│ max+1  │ Above maximum                         │\n└────────────────────────────────────────────────┘\n\nFor string inputs:\n- Empty string: \"\"\n- Single character: \"a\"\n- Maximum length\n- Maximum length + 1\n- Only whitespace: \"   \"\n- Leading\u002Ftrailing whitespace: \" test \"\n```\n\n### Special Input Values\n\n```\nEMPTY\u002FNULL\u002FMISSING:\n- null\n- undefined\n- Empty string \"\"\n- Empty array []\n- Empty object {}\n- Whitespace only\n- Missing required fields\n\nNUMERIC EDGE CASES:\n- 0, -0\n- Negative numbers\n- Decimals (0.1, 0.01)\n- Scientific notation (1e10)\n- MAX_INT, MIN_INT\n- MAX_INT + 1 (overflow)\n- Infinity, -Infinity\n- NaN\n\nSTRING EDGE CASES:\n- Unicode: \"Ṁöñᵗý Ṗẏẗḧöñ\"\n- Emojis: \"😀🎉🔥\"\n- RTL text: \"مرحبا\"\n- Null byte: \"test\\x00injection\"\n- Very long strings (10KB+)\n- Format strings: \"%s %n %d\"\n- Path traversal: \"..\u002F..\u002F..\u002Fetc\u002Fpasswd\"\n\nDATE\u002FTIME EDGE CASES:\n- Leap years (Feb 29)\n- Daylight saving transitions\n- End of month (Jan 31 → Feb 28)\n- End of year (Dec 31 → Jan 1)\n- Time zone boundaries\n- Unix epoch (1970-01-01)\n- Y2K-style dates (2038 problem)\n- Far future dates\n```\n\n### State Transition Testing\n\n```\nTest all valid transitions AND invalid ones:\n\nORDER STATUS:\n┌────────┐    ┌───────────┐    ┌────────┐\n│ Draft  │───►│ Confirmed │───►│Shipped │\n└────────┘    └───────────┘    └────────┘\n     │              │              │\n     ▼              ▼              ▼\n┌────────┐    ┌───────────┐    ┌────────┐\n│Cancelled│   │ Cancelled │    │Delivered│\n└────────┘    └───────────┘    └────────┘\n\nTest:\n✓ Valid: Draft → Confirmed → Shipped → Delivered\n✓ Valid: Confirmed → Cancelled\n✗ Invalid: Shipped → Draft (should fail)\n✗ Invalid: Delivered → Confirmed (should fail)\n```\n\n### Error Condition Testing\n\n```\nNETWORK ERRORS:\n- Connection timeout\n- Connection refused\n- DNS failure\n- SSL certificate errors\n- Partial response\n- Corrupted response\n\nRESOURCE ERRORS:\n- Disk full\n- Out of memory\n- Too many open files\n- Permission denied\n- File locked\n\nCONCURRENCY ERRORS:\n- Race conditions\n- Deadlocks\n- Lost updates\n- Double submissions\n```\n\n## Session-Based Test Management\n\n### Session Metrics\n\n```\nSESSION REPORT:\n┌─────────────────────────────────────────────────────────────┐\n│ Tester: [Name]                                              │\n│ Charter: [Title]                                            │\n│ Date: [Date]           Duration: [Actual time]              │\n├─────────────────────────────────────────────────────────────┤\n│ TIME BREAKDOWN:                                              │\n│ ┌────────────────────────────────────────────────────────┐ │\n│ │ Testing:        ████████████████████ 60%              │ │\n│ │ Bug Investigation: ██████████ 25%                      │ │\n│ │ Setup\u002FOverhead:    █████ 15%                           │ │\n│ └────────────────────────────────────────────────────────┘ │\n├─────────────────────────────────────────────────────────────┤\n│ OUTCOMES:                                                    │\n│ Bugs filed: [count]                                         │\n│ Questions raised: [count]                                   │\n│ Test ideas generated: [count]                               │\n│ Coverage areas: [list]                                      │\n├─────────────────────────────────────────────────────────────┤\n│ FOLLOW-UP:                                                   │\n│ - [Next charter suggestion]                                 │\n│ - [Area needing more coverage]                              │\n└─────────────────────────────────────────────────────────────┘\n```\n\n### Coverage Visualization\n\n```\nFEATURE COVERAGE MAP:\n\nFeature                Testing Coverage\n─────────────────────────────────────────\nLogin                  ████████████████ 100%\nRegistration           ████████████░░░░  75%\nSearch                 ████████░░░░░░░░  50%\nCheckout               ████████████████ 100%\nProfile                ████░░░░░░░░░░░░  25%\nAdmin                  ░░░░░░░░░░░░░░░░   0%\n\nLegend: █ Tested  ░ Not tested\n```\n\n## Bug Reporting\n\n### Bug Report Template\n\n```markdown\n# BUG-[ID]: [Descriptive Title]\n\n## Summary\n[One sentence description]\n\n## Environment\n- Browser\u002FDevice: [e.g., Chrome 120 on macOS]\n- URL: [where it occurred]\n- User: [role\u002Faccount type]\n\n## Steps to Reproduce\n1. [First step]\n2. [Second step]\n3. [Third step]\n\n## Expected Result\n[What should happen]\n\n## Actual Result\n[What actually happened]\n\n## Evidence\n- Screenshot: [attached]\n- Video: [link]\n- Console log: [attached]\n\n## Severity\n[Critical \u002F High \u002F Medium \u002F Low]\n\n## Notes\n[Additional context, related issues, workarounds]\n```\n\n### Severity Guidelines\n\n| Level | Definition | Example |\n|-------|------------|---------|\n| **Critical** | System unusable, data loss | Payment double-charging |\n| **High** | Major feature broken | Cannot complete checkout |\n| **Medium** | Feature impaired, workaround exists | Search requires exact match |\n| **Low** | Minor issue, cosmetic | Alignment off by 2px |\n\n## Best Practices\n\n### Do\n\n- **Time-box sessions** - 60-90 minutes max before break\n- **Take notes continuously** - Capture observations as you go\n- **Follow your curiosity** - Interesting behavior often hides bugs\n- **Vary your approach** - Don't test the same way every time\n- **Question everything** - \"Is this right?\" should be constant\n- **Document coverage** - Know what you've tested and what remains\n\n### Avoid\n\n- **Random clicking** - Exploration should be purposeful\n- **Only happy paths** - Edge cases hide the interesting bugs\n- **Ignoring instincts** - \"That's weird\" often leads to bugs\n- **Testing in isolation** - Consider the full user journey\n- **Rushing** - Quality exploration takes focused time\n\n## References\n\n- [Charter Templates](examples\u002Fcharters.md) - Ready-to-use charter templates\n- [Heuristic Quick Reference](reference.md) - Printable heuristic cards\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fquality\u002Fexploratory-testing",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill exploratory-testing",{"tool":64,"command":65},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill exploratory-testing",{"tool":67,"command":68},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill exploratory-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fquality\u002Fexploratory-testing\u002FSKILL.md",true,[],[73,82,90,98,106,114],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":81},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":81},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":81},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":81},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":81},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]