Test Design Principles and Helpful Tips
Learn how to maximize your test design skills and navigate the trickier aspects of Hexawise functionality.
By Justin and 3 others4 authors17 articles
- Why do most software tests suck?
- What do well-designed software tests look like?
- Prioritization: how should we get the biggest "bang for the buck" in a limited number of software tests?
- Best Practices for Effective Software Testing
- Manage regression tests at the "model level" to save time and avoid ever-increasing numbers of tests
- Important lessons from "20 Questions"
- Follow the "Goldilocks Rule" to determine the correct model scope
- Use Equivalence Classes or similar methods rather than long lists of Values
- Do not include Expected Results as Hexawise Parameters
- How to Handle Expected Results in Hexawise
- Different types of negative tests need to be handled differently when using Hexawise
- Hexawise Process - Sharing and Maintenance
- Defect Analysis After Hexawise
- Tips for Starting Points in Hexawise