 |
Home > Detail: The Simplest Automated Unit Test Framework That Could Possibly Work
Viewing Item 1 of 1289
|  |  |
| | |
The Simplest Automated Unit Test Framework That Could Possibly Work
By Chuck Allison
  
Summary: The title of this article is a variation on a theme from Extreme Programming (XP). XP is a code-centric discipline for getting software done right, on time, within budget, while having fun along the way. Quit laughing. The XP approach is to take the best software practices to the extreme. For example, if code reviews are good, then code should be reviewed constantly, even as it’s written, hence the XP practice of Pair Programming, where all code is written by two developers sharing a single workstation. One programmer pilots the keyboard while the other watches to catch mistakes and gives strategic guidance – then they switch roles as needed. The next day they may pair up with other folks. Likewise, if testing is good, then all tests should be automated and run many times per day. An ever-growing suite of unit tests should be executed whenever you create or modify any function, to ensure that the system is still stable. Furthermore, developers should integrate code into the complete, evolving system and run functional tests often (at least daily). | | |
|
|
View Content Detail:
• XDD3129filelistfilename1.pdf (742 Kb)
This paper was originally presented at STARWEST 2001 — a conference produced by Software Quality Engineering. For more information on this conference, visit the current STARWEST Web site.
About the Author
Chuck Allison is Assistant Professor of Computer Science at Utah Valley State College.
He is a contributing member of the C++ Standards Committee, Senior Editor for the
C/C++ Users Journal, and author of the book "C & C++ Code Capsules: A Guide for
Practitioners" (Prentice-Hall, 1998). He has taught C++ and Java extensively at
corporations throughout the United States. You can contact Chuck through his website
www.freshsources.com.
Back to Top
|
