[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70NGFJWNJHDKEYW9CVV7J7S":3,"skill-same:01M70NGFJWNJHDKEYW9CVV7J7S":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},"01M70NGFJWNJHDKEYW9CVV7J7S","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\u002Frsmdt-the-startup\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\u002Frsmdt-the-startup\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\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fquality\u002Fexploratory-testing\u002FSKILL.md",true,[],[73,90,124,148,170,190],{"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":6,"sourceHtmlUrl":77,"categories":78,"keywords":82,"publishedAt":43},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",[83,84,85,86,87,88,89],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"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":6,"sourceHtmlUrl":94,"categories":95,"keywords":104,"publishedAt":43},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[96,99],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[92,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":134,"publishedAt":43},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[130,131],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":132,"categoryName":133,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000036","内容创作者",[126,26,135,136,137,138,139,140,113,141,142,143,39,31,144,145,146,147],"content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":43},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[154],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},[156,157,126,158,159,146,160,161,162,163,164,165,166,167,111,168,39,31,105,169],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":180,"publishedAt":43},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[176,177,178,179],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":132,"categoryName":133,"taxonomyType":102,"taxonomyTypeDesc":103},[181,88,182,183,184,185,121,39,31,186,187,188,189],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":198,"publishedAt":43},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[196,197],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":132,"categoryName":133,"taxonomyType":102,"taxonomyTypeDesc":103},[199,88,200,109,201,187,39,182,185,31,188],"Rules","writing rules","project rules"]