GeekArticles 
Testing Bug ReportingTesting Component-Based Software
Author: stickyminds.com |
Published: 18th Aug 2005 |
Visited: 443 times |
Add CommentFiled in: Bug ReportingToday component engineering is gaining substantial interest in the software engineering community. Although a lot of research effort has been devoted to analysis methods and design strategies of component-based software, a few papers address the testing of component-based software. The paper identifies and classifies the testing issues of software components and component-based software according to working experience. It discusses component testability in terms of controllability, traceability, test suite, presentation, test support, and configuration management. The paper proposes a model to measure the maturity levels of a component testing process. Finally, it shares our observations and insights on test automation for component-based application systems.
Read Article Sponsored Links
Related Articles
• Advancing from Ajax Based Frameworks Frameworks have been in focus lately because of the integration of jQuery to Microsoft. Because of jQuery’ s feat and also of Microsoft frameworks were largely talked about again and compared. Unfortunately there are times wherein a developer would stand up and say the framework is better ...
• Swing Extreme Testing Book Review Swing Extreme Testing Book Review
Swing used to be a simple component offered as an add-on for Java. This plug-in can be used as a GUI (graphical user interface) to develop as an add-on for the Java application. It has the ability to emulate certain platforms eventually building a powerful applicat ...
• Swing Extreme Testing Swing Extreme Testing by Tim Lavers, Lindsay Peters
This book is a practical guide to automated software testing for extreme Java programming using Swing GUIs, with lots of ready-to-use real-life examples and source code for automated testing of the software components usually regarded as too hard ...
• 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 ShowerThread Class The ShowerThread Class
Since SaveAsDialog.show() blocks, we cannot call this from our main thread; instead we spawn a new thread. This thread could just be an anonymous inner class in the init()metho ...
• 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 ...
• Testing Multithreaded Java Code
In this interview from JavaOne 2008, Coverity chief scientist Andy Chou discusses why traditional unit tests often help in uncovering concurrency-related errors, and why a combination of static and dynamic analysis yields better results when testing multithreaded code.
...
