Hexawise Help Center
All Collections
Test Design Principles
Test Design Principles
+1
13 articles in this collection
Written by
Justin Hunter,
Ivan Filippov,
Scott Johnson
and 1 other
Defect Analysis After Hexawise
How to identify the defect reason after you move to combinatorial testing.
Written by
Ivan Filippov
Updated over a week ago
Thoughtful Test Design Example
See how a thorough set of inputs is selected from a web app to build a Hexawise model and generate optimized Given-When-Then test scenarios.
Written by
Ivan Filippov
Updated over a week ago
General
Why do most software tests suck?
The problems found in many manually-designed software tests.
Written by
Ivan Filippov
Updated over a week ago
What do well-designed software tests look like?
The qualities found in a well-designed, high-quality software test.
Written by
Scott Johnson
Updated over a week ago
Prioritization: how should we get the biggest "bang for the buck" in a limited number of software tests?
Premier strategies for getting the most out of every single software test.
Written by
Conor Wolford
Updated over a week ago
Best Practices for Effective Software Testing
A quick description of some best practices that should be adopted and followed among software test design teams.
Written by
Conor Wolford
Updated over a week ago
Manage regression tests at the "model level" to save time and avoid ever-increasing numbers of tests
Benefits of designing and updating your tests at the model level.
Written by
Scott Johnson
Updated over a week ago
Important lessons from "20 Questions"
Lessons learned from the game "20 Questions" applied to software testing.
Written by
Justin Hunter
Updated over a week ago
Hexawise-Specific
Use Equivalence Classes or similar strategies rather than long lists of Values
Input definition strategies for creating the most effective set of Hexawise tests.
Written by
Ivan Filippov
Updated over a week ago
Hexawise Process - Sharing and Maintenance
Tips and best practices for the long-term management of Hexawise plans
Written by
Ivan Filippov
Updated over a week ago
Follow the "Goldilocks Rule" to determine the correct amount of detail
Guidelines for how much detail to include in your Hexawise inputs.
Written by
Justin Hunter
Updated over a week ago
Do not include Expected Results as Hexawise Inputs
Expected results should not be included as "Inputs" in Hexawise
Written by
Conor Wolford
Updated over a week ago
Different types of negative tests need to be handled differently when using Hexawise
Strategies for creating and working with negative tests in Hexawise.
Written by
Justin Hunter
Updated over a week ago