10.12.2012 Views

Domain Testing: Divide and Conquer - Testing Education

Domain Testing: Divide and Conquer - Testing Education

Domain Testing: Divide and Conquer - Testing Education

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Jorgensen (2002) also asserted that this kind of testing is useful when<br />

variables are known to heavily interact with each other. However, this has similar<br />

shortcomings as with boundary value analysis when there are dependent variables<br />

involved.<br />

Beizer (1995) contended that extreme points combination testing might not<br />

be an effective test case generation technique. This is because the number of<br />

combinations increases exponentially with the number of input variables <strong>and</strong> when<br />

there are dependent variables involved, a large number of the tests that are<br />

generated might be meaningless. For example, certain combinations might be<br />

impossible due to certain dependency relationships among the input variables.<br />

2.02.04 Which Test Case Selection Method Should We Use?<br />

This thesis research has concluded that risk-based strategy is the best strategy,<br />

especially where cost <strong>and</strong> effective failure detection are concerned. R<strong>and</strong>om testing<br />

might be used as a supplement <strong>and</strong> might be valuable in high-volume automated<br />

test case execution. High-volume automated r<strong>and</strong>om testing would be inexpensive<br />

since it is automated, <strong>and</strong> having hundreds or thous<strong>and</strong>s of r<strong>and</strong>om test cases might<br />

help in finding any bugs that were not revealed by the risk-based strategy.<br />

In conclusion, risk-based selection of test cases is something that definitely<br />

needs to be done, but high-volume r<strong>and</strong>om test selection might be done in addition<br />

if time <strong>and</strong> resources permit, especially for regression testing. Kaner et al. (2002)<br />

have described regression testing as follows:<br />

Regression testing involves reuse of the same tests, so you can retest (with<br />

these) after change. There are three kinds of regression testing. You do bug<br />

fix regression after reporting a bug <strong>and</strong> hearing later on that it’s fixed. The<br />

goal is to prove that the fix is no good. The goal of old bugs regression is to<br />

prove that a change to the software has caused an old bug fix to become<br />

unfixed. Side-effect regression, also called stability regression, involves<br />

retesting of substantial parts of the product. The goal is to prove that the<br />

32

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!