Hexawise - Training
- 6. Why do most software tests suck?
- 7. What do well-designed software tests look like?
- 8. Prioritization: how should we get the biggest "bang for the buck" in a limited number of software tests?
- 9. Does pairwise testing really work? Evidence, data, and case studies.
- 10. Important lessons from 20 questions
- 11. Mistake to Avoid: Thinking "Hexawise won't help on my project, will it? My project is 'different.' "
- 12. Mistake to Avoid - Try not to use long lists of Values; instead, use Equivalence Classes and similar strategies
- 13. Tip: Use "Mixed-Strength" tests more often than "regular" higher-strength tests
- 14. Tip: Follow the "Goldilocks Rule" to determine the correct amount of detail
- 15. All-purpose troubleshooting tip when results do not come back: rename a test input and recalculate solutions if your results don't come back.
- 16. Tip: Start by creating 5 parameters for the 5 most obvious things that will be varied
- 17. Tip: Think carefully about which outcomes you want your tests to cover
- 18. Tip: Manage regression tests at the "model level" to save time and avoid ever-increasing numbers of tests
- 19. Tip: Different types of negative tests need to be handled differently when using Hexawise
- 20. TIP: Use the Plan Scorecard to Identify possible problems with your test plans
- 21. TIP: Use the "Freeze" feature to preserve test conditions
- 22. TIP: Use the Plan Scorecard to identify new features that could improve your tests
- 23. TIP: Use the Editable Mind Maps to edit your plan
- 24. TIP: How to Deal with "Select All That Apply" Scenarios