Here is a list of available tools:
http://www.pairwise.org/tools.asp
But want to draw out personal experiences of SO members.
Current tool is FireEye but we are looking for other tools.
Here is a list of available tools:
http://www.pairwise.org/tools.asp
But want to draw out personal experiences of SO members.
Current tool is FireEye but we are looking for other tools.
I'm a big fan of PICT - but probably because it's our (Microsoft's) primary combinatorial testing tool.
Perhaps more of a site note, but I just bumped into this interesting article on the effectiveness of pairwise, or actually N-way, testing:
D. Richard Kuhn, Dolores R. Wallace, Albert M. Gallo: Software Fault Interactions and Implications for Software Testing. IEEE Trans. Software Eng. 30(6): 418-421 (2004) Software Fault Interactions and Implications for Software Testing pdf
Abstract:
Exhaustive testing of computer software is intractable, but empirical studies of software failures suggest that testing can in some cases be effectively exhaustive. Data reported in this study and others show that software failures in a variety of domains were caused by combinations of relatively few conditions. These results have important implications for testing. If all faults in a system can be triggered by a combination of n or fewer parameters, then testing all n-tuples of parameters is effectively equivalent to exhaustive testing, if software behavior is not dependent on complex event sequences and variables have a small set of discrete values.