Testing is important part in software development cycle. Test case generation can be done either through analysis (white box testing) or from the input/ output relation (black box testing).
for large systems that have many interacted parameters (variables) with options (values) it is desired to test using systematic approaches. One of these approaches is t-way testing, where t is the strength of coverage.
The Generation of test case that covers each pairs of parameters is called pair
wise testing (t=2) , and covers each triples called 3-way testing and so forth.
the generation of test case is NP_completeness problem( no unique solution for minimal number of test case) and so different strategies exist.
The strategies that cover variable t are called n-way strategies.

During testing of many software we find that code coverage is doing well with pairwise testing.

The question here how we can find suitable case study that required n-way testing?

With google!

Sounds like a homework question to me?

I know little bit about testing field, but I am not getting exact answer for your problem

Welcome friend,

It's ok. But How one can formalize the parameters and doing the test??



Welcome friend.
Actually its real discussion rather than h/w. The result we optain mean that the programmers put non_interacted parameters in their applications. So, It is hard to find such system that really required N-way interaction.





Welcome friend.
Don't worry. But when you find such as system notify us.
Regards.

This post has been edited by miy_alkhiro: 6 Jun, 2008 - 07:10 PM

As professional test engineer I am going to reply to it.
For all my carrear I have never heard of n-way testing, neither in my testing courses nor from someone. Though, I presume that if your program does execute some business workflow (a way) or many of them (the ways) then this might be a case. In other words, n--way testing would be E2E test back and forth with respect to the test paths that are possible in your application. What I mean by "test path" is just a test scenario that includes sequence of test steps in the logical order.
Though if we are talking about path or branch tests (white-box methodology) then n-way might be execution/test of this variable throughout all code units.
Also I assume that n-way testing means something else, something that is just called the way I did not get use to. You will need to ask QA guys for that, or more likely - methodology QA guys. It's all about theory, IMHO, that's from the Brainbench pool of questions.

Thx.

This post has been edited by davegeek: 5 Aug, 2008 - 07:10 AM