Object-oriented software construction (2nd ed.)
Object-oriented software construction (2nd ed.)
Component-based software engineering: putting the pieces together
Component-based software engineering: putting the pieces together
Test Driven Development: By Example
Test Driven Development: By Example
Testing Software Components Using Boundary Value Analysis
EUROMICRO '03 Proceedings of the 29th Conference on EUROMICRO
Eclipse Cookbook
Application of built-in-testing in component-based embedded systems
Proceedings of the ISSTA 2006 workshop on Role of software architecture for testing and analysis
Feature Diagrams and Logics: There and Back Again
SPLC '07 Proceedings of the 11th International Software Product Line Conference
IEEE Transactions on Software Engineering
CBSE'06 Proceedings of the 9th international conference on Component-Based Software Engineering
An analysis of unit tests of a flight software product line
Science of Computer Programming
An analysis of unit tests of a flight software product line
Science of Computer Programming
| Hi-index | 0.00 |
Test Driven Development (TDD) is a process for software engineering that advocates constructing test cases before writing actual code; indeed, coding is treated as an exercise in validating the test cases. While such an approach appeals to many software developers, one cannot simply apply TDD to component-based software engineering (CBSE). The primary obstacle is the more complex life cycle for software components that must be packaged, deployed and executed within software containers or deployment environments. In this paper we describe two case studies that show different ways by which TDD can be applied to CBSE. Our focus remains on the dependencies that exist between components and how to manage these dependencies during testing to still enable successful unit testing.