All-pairs testing

In computer science, all-pairs testing or pairwise testing is a combinatorial method of software testing that, for each pair of input parameters to a system (typically, a software algorithm), tests all possible discrete combinations of those parameters. Using carefully chosen test vectors, this can be done much faster than an exhaustive search of all combinations of all parameters, by "parallelizing" the tests of parameter pairs.

Rationale

The most common bugs in a program are generally triggered by either a single input parameter or an interaction between pairs of parameters.^[1] Bugs involving interactions between three or more parameters are both progressively less common ^[2] and also progressively more expensive to find---such testing has as its limit the testing of all possible inputs.^[3] Thus, a combinatorial technique for picking test cases like all-pairs testing is a useful cost-benefit compromise that enables a significant reduction in the number of test cases without drastically compromising functional coverage.^[4]

More rigorously, if we assume that a test function has $N$ parameters given in a set $\{P_{i}\}=\{P_{1},P_{2},...,P_{N}\}$ . The range of the parameters are given by $R(P_{i})=R_{i}$ . Let's assume that $|R_{i}|=n_{i}$ . We note that the all possible conditions that can be used is an exponentiation, while imagining that the code deals with the conditions taking only two pair at a time, might reduce the number of conditions.

To demonstrate, suppose there are X,Y,Z parameters. We can use a predicate of the form $P(X,Y,Z)$ of order 3, which takes all 3 as input, or rather three different order 2 predicates of the form $p(u,v)$ . $P(X,Y,Z)$ can be written in an equivalent form of $p_{{xy}}(X,Y),p_{{yz}}(Y,Z),p_{{zx}}(Z,X)$ where comma denotes any combination. If the code is written as conditions taking "pairs" of parameters, then the set of choices of ranges $X=\{n_{i}\}$ can be a multiset, because there can be multiple parameters having same number of choices.

$max(S)$ is one of the maximum of the multiset $S$ The number of pair-wise test cases on this test function would be:- $T=max(X)\times max(X\setminus max(X))$

Therefore, if the $n=max(X)$ and $m=max(X\setminus max(X))$ then the number of tests is typically O(nm), where n and m are the number of possibilities for each of the two parameters with the most choices, and it can be quite a lot less than the exhaustive $\prod n_{i}$ ·

N-wise testing

N-wise testing can be considered the generalized form of pair-wise testing.

The idea is to apply sorting to the set $X=\{n_{i}\}$ so that $P=\{P_{i}\}$ gets ordered too. Let the sorted set be a $N$ tuple :-

$P_{s}=<P_{i}>\;;\;i<j\implies |R(P_{i})|<|R(P_{j})|$

Now we can take the set $X(2)=\{P_{{N-1}},P_{{N-2}}\}$ and call it the pairwise testing. Generalizing further we can take the set $X(3)=\{P_{{N-1}},P_{{N-2}},P_{{N-3}}\}$ and call it the 3-wise testing. Eventually, we can say $X(T)=\{P_{{N-1}},P_{{N-2}},...,P_{{N-T}}\}$ T-wise testing.

The N-wise testing then would just be, all possible combinations from the above formula.

Example

Consider the parameters shown in the table below.

Parameter name	Value 1	Value 2	Value 3	Value 4
Enabled	True	False	*	*
Choice type	1	2	3	*
Category	a	b	c	d

'Enabled', 'Choice Type' and 'Category' have a choice range of 2, 3 and 4, respectively. An exhaustive test would involve 24 tests (2 x 3 x 4). Multiplying the two largest values (3 and 4) indicates that a pair-wise tests would involve 12 tests. The pict tool generated pairwise test cases is shown below.

Enabled	Choice type	Category
True	3	a
True	1	d
False	1	c
False	2	d
True	2	c
False	2	a
False	1	a
False	3	b
True	2	b
True	3	d
False	3	c
True	1	b

Notes

↑ Black, Rex (2007). Pragmatic Software Testing: Becoming an Effective and Efficient Test Professional. New York: Wiley. p. 240. ISBN 978-0-470-12790-2.
↑ Kuhn, D. Richard; Wallace, Dolores R.; Gallo, Albert M., Jr. (June 2004). "Software Fault Interactions and Implications for Software Testing" (PDF). IEEE Trans. on Software Engineering. 30 (6): 1–4.
↑ Kuhn, D. Richard; Kacker, Raghu N.; Yu Lei (October 2010). Practical Combinatorial Testing. SP 800-142. (Report). National Institute of Standards and Technology. doi:10.6028/NIST.SP.800-142.
↑ "IEEE 12. Proceedings from the 5th International Conference on Software Testing and Validation (ICST). Software Competence Center Hagenberg. "Test Design: Lessons Learned and Practical Implications.". July 18, 2008. pp. 1–150. doi:10.1109/IEEESTD.2008.4578383.

External links

This article is issued from Wikipedia - version of the 12/3/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.