GeekArticles 
Testing Testing BasicsWhy Bother to Unit Test?
Author: ipl.com |
Published: 12th Aug 2005 |
Visited: 421 times |
Add CommentFiled in: Testing BasicsWhy Bother to Unit Test?
This paper addresses a question often posed by developers who are new to the concept
of thorough testing: Why bother to unit test? The question is answered by adopting the
position of devil's advocate, presenting some of the common arguments made against
unit testing, then proceeding to show how these arguments are worthless. The case for
unit testing is supported by published data.
Read Article Sponsored Links
Related Articles
• Swing Extreme Testing - Outline of the Unit Test Outline of the Unit Test
The things we want to test are:
Initial settings:
The text field is empty.
The text field is a sensible size.
The Ok button is disabled.
The Cancel button is enabled.
The dialog is a sensible size.
...
• Swing Extreme Testing - Unit Test Infrastructure Unit Test Infrastructure
Having seen the broad outline of the test class and the UI methods needed, we can look closely at the implementation of the test. start with the UI Wrapper class and the init() and cleanup()method ...
• Swing Extreme Testing - The wasCancelled() Test The wasCancelled() Test
The first of our API tests is to check the wasCancelled() method. We will basically do three investigations. The first test will call wasCancelled()before the dialog has been cancelled. The second test will cancel the dialog and then call the method. In the third test we wil ...
• Swing Extreme Testing - The Data Validation Test The Data Validation Test
The Ok button of the SaveAsDialog should only be enabled if the name that has been entered is valid. A name can be invalid if it contains an illegal character, or if it has already been use ...
• Memory leak when dynamically loading DLL with Dialogs unit uses QC#: 58918 Version: 11.2 Status: Open defect, requires resolution Description: There is a memory leak when DLL are dynamically loading and unloading when the Dialogs or Controls units are in uses.
This a critical bug when the DLL is used by a windows ...
