Due To time Constraints, everything cannot be tested. Take an eg.
You have to test a S/W on English/French/Japanese and German Languages with OS as VISTA/MAC PPC/IMAC/WINXP Testing all will take 16 Language-OS Combination But as French/English/German are Roman Lang and Japanese is double byte lang so u can omit some of the combinations here. Similarly IMAC and MAC PPc can be grouped in one pair. VISTA and WIN XP in other pair Now depending upon time , you can select the number of combinations u want to test eg IMAC- GERman MAC PPC-- French IMAC- Japanese VISTA- Japanese WINXP - German VISTA- English
Above answer was rated as good by the following members: sweetruler
We've all heard the phrase You can't test everything. This axiom is particularly appropriate for testing multiple combinations of options selections and configurations. To test all combinations in some of these instances would require millions of tests. A systematic way to reduce the number of tests is called pair-wise testing.
Pairwise (a.k.a. all-pairs) testing is an effective test case generation technique that is based on the observation that most faults are caused by interactions of at most two factors. Pairwise-generated test suites cover all combinations of two therefore are much smaller than exhaustive ones yet still very effective in finding defects.
Another definition:->
Pairwise testing is a specification-based testing criterion which requires that for each pair of input parameters of a system every combination of valid values of these two parameters be covered by at least one test case. In this paper we propose a new test generation strategy for pairwise testing.
Pair-wise testing is a ad-hoc/monkey testing techniques used in case of lack of time lack of documentation lack of skills lack of resources etc.. The test lead/p.m will use this technique due to lack of time. They will make a tester as a pair with developer. They both continue the coding and testing parallel.
Pairwise (a.k.a. all-pairs) testing is an effective test case generation technique that is based on the observation that most faults are caused by interactions of at most two factors. Pairwise-generated test suites cover all combinations of two therefore are much smaller than exhaustive ones yet still very effective in finding defects.
I heared pair-wise testing is also termed as Orthogonal Array testing.I read about Orthogonal testing technique but i didn't understand how the combinations are reduced.Can anybody explain with example?
Pairwise testing is an effective test case generation technique that is based on the observation that most faults are caused by interactions of at most two factors. Pairwise-generated test suites cover all combinations of two therefore are much smaller than exhaustive ones yet still very effective in finding defects.
Due To time Constraints everything cannot be tested. Take an eg.
You have to test a S/W on English/French/Japanese and German Languages with OS as VISTA/MAC PPC/IMAC/WINXP Testing all will take 16 Language-OS Combination But as French/English/German are Roman Lang and Japanese is double byte lang so u can omit some of the combinations here. Similarly IMAC and MAC PPc can be grouped in one pair. VISTA and WIN XP in other pair Now depending upon time you can select the number of combinations u want to test eg IMAC- GERman MAC PPC-- French IMAC- Japanese VISTA- Japanese WINXP - German VISTA- English
Pair Testing is a type of Ad-hoc testing. When ever test engineers found the risk in functional and system testing like lack of time lack of knowledge then they'll conduct the functional and system testing in Ad-hoc manner. That is coducting the testing in informal manner without follwing any formal testing type.
Pair means group together with testers and developeres. due to the lack of time developers and testers together to do the development and testing.
Pair wise testing is a type of adhoc teting. Mainly done at a point where the testers do not have the sufficient knowledge about the data needed to carry out testing. Here the juniour testers are paired with senoir ones to share their knowledge on domain testing.
0 
1