Explain All-pairs testing?
Answer / ramyab.mca@gmail.com
Hai....
All-pairs testing:
All-pairs testing or pair wise testing is a combinatorial
software testing method 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. 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.
the simplest bugs in a program are generally triggered by a
single input parameter. The next simplest category of bugs
consists of those dependent on interactions between pairs
of parameters, which can be caught with all-pairs testing.
[1] Bugs involving interactions between three or more
parameters are progressively less common[2], whilst at the
same time being progressively more expensive to find by
exhaustive testing, which has as its limit the exhaustive
testing of all possible inputs.
K,Byeeee...
Thanks & Regards
B.Ramyasri
Is This Answer Correct ? | 0 Yes | 0 No |
how to check security of any browser??give me some ex.?
what is migration testing?
what is adhoc testing n when it wil be done?
what are the testing appraoch that you have tested for Pencil
Do the test cases differ for Functional,Integration,System and User Acceptance Testing???
Hi Friends, I've to submit a presentation in my office about "Different bug tracking tools" ? Where can i find (or any site) the templates for the bug tracking tools.
diff b/w regression, re-testing & repeative testing
what is scenario????
Can you explain v model in manual testing?
In an ATM machine , after entering pin -> not able to withdraw money. What are all the possible reasons. Debug
What is the difference between Project Based Testing and Product Based Testing?
18 Answers Pramati Technologies, Satyam,
What are the prototypes are used during the integration testing ?Explain the stub and the driver in details?Are the stub and the driver both are used in top-down and the bottom-up approaches ?