|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Point/Counterpoint
May/June 2007 (vol. 24 no. 3)
pp. 80-83
| ASCII Text | x | ||
| Steve Freeman, Nat Pryce, Joshua Kerievsky, "Point/Counterpoint," IEEE Software, vol. 24, no. 3, pp. 80-83, May/June, 2007. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2007.84, author = {Steve Freeman and Nat Pryce and Joshua Kerievsky}, title = {Point/Counterpoint}, journal ={IEEE Software}, volume = {24}, number = {3}, issn = {0740-7459}, year = {2007}, pages = {80-83}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2007.84}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Point/Counterpoint IS - 3 SN - 0740-7459 SP80 EP83 EPD - 80-83 A1 - Steve Freeman, A1 - Nat Pryce, A1 - Joshua Kerievsky, PY - 2007 KW - mock objects KW - object-oriented programming KW - program testing KW - test-driven development VL - 24 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2007.84
"Point Argument: Mock Objects: Find Out Who Your Friends Are," by Steve Freeman and Nat Pryce. Mock objects help guide object-oriented programming by concentrating on what objects do, no what they are. "Counterpoint Argument: "TDD: Don't Much It Up with Too Many Mocks," by Joshua Kerievsky. Routinely test-driving code with mock objects leads to premature object composition, hard-to-read and fragile code, and lost time. This department is part of a special issue on test-driven development.
Index Terms:
mock objects, object-oriented programming, program testing, test-driven development
Citation:
Steve Freeman, Nat Pryce, Joshua Kerievsky, "Point/Counterpoint," IEEE Software, vol. 24, no. 3, pp. 80-83, May-June 2007, doi:10.1109/MS.2007.84
Usage of this product signifies your acceptance of the Terms of Use.