What works & What doesn’t! (Limitations?) Applying OATS manually is not advisable. Focusing the testing effort on the wrong area of the application. Picking the wrong parameters to combine. Orthogonal array only tests the most optimal combinations and not all. Use your testing skills, expertise, and experience to improve the test cases produced by these methods.
Benefits of OA Implementation time is less: The implementation time is less, as the test cases are less. Even though the test suit count is less, the combination will be optimum and covers the basic feature completely. Execution time is less: As the test cases are less in new test suite, execution time is also less. Result analysis takes less time: Time taken to compare the result files with the standard files is less. This reduces the overall test execution time. Increase in overall productivity: All the above points provide evidence to the fact that the OA methodology increases the overall productivity as lesser number of test cases are written. Implementation
time, test execution time and the result analysis time is less compared to the other methods. Hence, OA concept increases the overall productivity by 40%-50%. High code coverage: As evidenced in the join index experience, OA methodology covers close to 95% of the feature code compared to the usual methods. This is achieved with less number of test cases and with less execution time. For the remaining 5% of the code, tests have to be written manually. In this way, close to 100% of the feature code is covered.
Conclusion “We can save time and effort and find bugs efficiently by testing variables and values in combination.” It is beneficial to the Software product testing to make use of the Orthogonal Arrays. The only constraint would be the applicability of the concept to certain types of products. There are 3 areas in a product life cycle management where we can benefit: Test case development for new feature/product Re designing the existing test cases Sustenance of the test cases thus developed. The most critical portion of the adoption process is the product understanding and modeling the product/ feature as parameters and levels. The care and efforts put in to develop this model will drive the success of the test suite design.
References Good book on OA “Orthogonal Arrays, Theory and Applications, by A.S.Hedayat, N.J.A Sloane, and John Stufken http://www.phadkeassociates.com/index_rdexperttestplanning.htm http://www.pairwise.org/tools.asp http://www.combinatorialtesting.com/ clear-introductions-1 http://www.slideshare.net/Softwarecentral/ test-smarter-with-pairwise-testing
Many of you store your personal or professional documents in the cloud in Google Drive, DropBox, box.net or Skydrive. We know that these services do peek into your files. What if we can add a layer of security without loosing the flexibility of accessing these files from any of your devices. Here are two solutions that you can use. These technologies encrypt your files on the device, not in the cloud https://boxcryptor.com http://www.viivo.com
IDC Tech Journal — January 2014
All single-mode defects can be found if every option is tested at least once (unit elements) 2-way or “Pair-wise” is combination of 2 items (parameters) that cause a defect 3-way or “Tri-wise” is combination of 3 items (parameters) that cause a defect “Pair-wise” defect detection (pair-wise testing) finds most defects, ex. testing all pairs typically finds 75% of defects Source: Kuhn NASA Deep Space Mission - study showed that 88% of bugs discovered using “pair-wise” defect detection testing U.S. Food and Drug Administration – study showed 98% bugs discovered using “pair-wise” defect detection. Source: 27th NASA / IEEE Software Engineering Workshop, NASA Goddard Space Flight Center, 4-6 Dec, 2002.
11 p