Abstract | ||
---|---|---|
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. |
Year | DOI | Venue |
---|---|---|
2009 | 10.1007/978-3-642-02414-6_16 | CBSE |
Keywords | Field | DocType |
software component,software container,successful unit testing,inter-component dependencies,software components,approach appeal,unit testing,component-based software engineering,actual code,test driven development,software engineering,software developer,test case,component based software engineering,software development | System integration testing,Systems engineering,Software engineering,Computer science,Real-time computing,Regression testing,Software reliability testing,Component-based software engineering,Software construction,Software development,Software measurement,Software sizing | Conference |
Volume | ISSN | Citations |
5582 | 0302-9743 | 4 |
PageRank | References | Authors |
0.47 | 8 | 1 |
Name | Order | Citations | PageRank |
---|---|---|---|
George T. Heineman | 1 | 476 | 65.84 |