|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
A Close Look at Domain Testing
July 1982 (vol. 8 no. 4)
pp. 380-390
| ASCII Text | x | ||
| L.A. Clarke, J. Hassell, D.J. Richardson, "A Close Look at Domain Testing," IEEE Transactions on Software Engineering, vol. 8, no. 4, pp. 380-390, July, 1982. | |||
| BibTex | x | ||
| @article{ 10.1109/TSE.1982.235572, author = {L.A. Clarke and J. Hassell and D.J. Richardson}, title = {A Close Look at Domain Testing}, journal ={IEEE Transactions on Software Engineering}, volume = {8}, number = {4}, issn = {0098-5589}, year = {1982}, pages = {380-390}, doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.1982.235572}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - JOUR JO - IEEE Transactions on Software Engineering TI - A Close Look at Domain Testing IS - 4 SN - 0098-5589 SP380 EP390 EPD - 380-390 A1 - L.A. Clarke, A1 - J. Hassell, A1 - D.J. Richardson, PY - 1982 KW - test data selection KW - Program testing VL - 8 JA - IEEE Transactions on Software Engineering ER - | |||
White and Cohen have proposed the domain testing method, which attempts to uncover errors in a path domain by selecting test data on and near the boundary of the path domain. The goal of domain testing is to demonstrate that the boundary is correct within an acceptable error bound. Domain testing is intuitively appealing in that it provides a method for satisfying the often suggested guideline that boundary conditions should be tested.
Index Terms:
test data selection, Program testing
Citation:
L.A. Clarke, J. Hassell, D.J. Richardson, "A Close Look at Domain Testing," IEEE Transactions on Software Engineering, vol. 8, no. 4, pp. 380-390, July 1982, doi:10.1109/TSE.1982.235572
Usage of this product signifies your acceptance of the Terms of Use.