test-design-istqb
Skill5 starsChanged 9 months agoMITView on GitHub
Apply ISTQB Foundation Level test design techniques including equivalence partitioning, boundary value analysis, decision tables, and state transition testing to create comprehensive test cases.
In this repository10 other files it gives its agents.
- browser-useSkill
- cicd-testing-integrationSkill
- defect-lifecycle-managerSkill
- find-skillsSkill
- multi-agent-orchestrationSkill
- qa-process-improvementSkill
- skill-creatorSkill
- test-execution-managerSkill
- user-story-static-verifierSkill
- senior-qa-engineerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 17 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when you need to:
- Distinctive: line 15
Create test data specifications
- Distinctive: line 16
Ensure comprehensive test coverage
- Distinctive: line 28
Create one test case per partition
- Distinctive: line 42
What it is: Test at the edges of equivalence partitions where defects often hide.
- Distinctive: line 46
Test: min-1, min, min+1, max-1, max, max+1
- Distinctive: line 57
What it is: Test combinations of conditions and their resulting actions.
- Distinctive: line 62
Create table with all meaningful combinations
- Distinctive: line 82
What it is: Test how system behavior changes based on state and events.
- Distinctive: line 88
Test all valid paths
- Distinctive: line 89
Test invalid transitions for error handling
- Distinctive: line 108
What it is: Use experience to anticipate common defects.
- Distinctive: line 143
Ensure test design includes:
- Distinctive: line 165
Start with happy path, then add negative cases
- Distinctive: line 166
Use meaningful test case IDs with prefixes
- Distinctive: line 167
Keep test cases atomic (one objective per test)
- Distinctive: line 171
Update tests when requirements change
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test Design - ISTQB Techniques
Expert skill for designing comprehensive test cases using ISTQB Foundation Level test design techniques.
When to Use
Use this skill when you need to:
- Design test cases from requirements
- Apply black-box testing techniques
- Create test data specifications
- Ensure comprehensive test coverage
- Generate test scenarios for positive, negative, and edge cases
ISTQB Test Design Techniques
1. Equivalence Partitioning
What it is: Divide input domains into classes where all members should be treated the same.
How to apply:
- Identify all inputs and outputs
- Determine valid and invalid partitions
- Create one test case per partition
- Cover both valid and invalid classes
Example:
Requirement: Age must be 18-65
Partitions:
- Invalid: < 18 (e.g., 17)
- Valid: 18-65 (e.g., 30)
- Invalid: > 65 (e.g., 66)2. Boundary Value Analysis
What it is: Test at the edges of equivalence partitions where defects often hide.
How to apply:
- Identify boundaries in requirements
- Test: min-1, min, min+1, max-1, max, max+1
- Focus on limits, ranges, and thresholds
Example:
Requirement: Password 8-20 characters
Test values: 7, 8, 9, 19, 20, 21 characters3. Decision Tables
What it is: Test combinations of conditions and their resulting actions.
How to apply:
- Identify conditions (inputs/states)
- List possible actions (outputs/behaviors)
- Create table with all meaningful combinations
- Generate test cases from each column
Example:
Condition 1: Premium customer? (Y/N)
Condition 2: Order > $100? (Y/N)
| Premium | Order>$100 | Discount |
|---------|-----------|----------|
| Y | Y | 20% |
| Y | N | 10% |
| N | Y | 10% |
| N | N | 0% |
= 4 test cases4. State Transition Testing
What it is: Test how system behavior changes based on state and events.
How to apply:
- Identify all states
- Map valid transitions
- Identify invalid transitions
- Test all valid paths
- Test invalid transitions for error handling
Example:
Order States: Draft → Submitted → Approved → Shipped → Delivered
Valid transitions:
- Draft → Submitted
- Submitted → Approved
- Approved → Shipped
- Shipped → Delivered
Invalid transitions to test:
- Draft → Shipped (should reject)
- Delivered → Draft (should reject)5. Error Guessing
What it is: Use experience to anticipate common defects.
Common areas:
- Empty/null values
- Special characters
- Boundary conditions
- Concurrent access
- Network failures
- Timeout scenarios
Test Case Template
Test Case ID: TC-XXX
Title: [Clear, descriptive title]
Preconditions: [System state before test]
Test Data: [Specific values to use]
Steps:
1. [Action]
2. [Action]
3. [Action]
Expected Results:
1. [Expected outcome]
2. [Expected outcome]
3. [Expected outcome]
Actual Results: [Filled during execution]
Status: [Pass/Fail]
Notes: [Any observations]Coverage Checklist
Ensure test design includes:
- ✓ Positive scenarios (happy path)
- ✓ Negative scenarios (error handling)
- ✓ Edge cases (boundaries)
- ✓ Data validation tests
- ✓ State transitions
- ✓ Error messages verification
- ✓ Performance considerations
- ✓ Security aspects
- ✓ Usability/UX validation
Test Design Output
Deliverables:
- Test cases with clear steps and expected results
- Test data specifications with valid/invalid examples
- Traceability matrix linking requirements to tests
- Coverage analysis showing technique application
- Risk assessment highlighting critical test areas
Best Practices
- Start with happy path, then add negative cases
- Use meaningful test case IDs with prefixes
- Keep test cases atomic (one objective per test)
- Make steps reproducible by anyone
- Include cleanup/teardown procedures
- Review test cases with team
- Update tests when requirements change
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

