No matter which tools, techniques, and methodologies are used for software development, it remains an error-prone process. Nevertheless, changing such important constituents of the software process surely has an effect on the types of faults inherent in the developed software. For instance, some types of faults are typical for structured development, whereas others are typical for object-oriented development.
This chapter explores the question of whether component-based software requires new testing techniques, and proposes an integrated testing technique. This technique integrates various tasks during testing component-based software: whiteand black-box testing of the main component (i.e., the top level component controlling the other components), black-box testing of components, black-box testing of the middleware and integration testing of the main component with other components. Benefits of this technique are shown using a real-world example: the technique is automatable and applicable to existing component-based software.
| Identifer | oai:union.ndltd.org:DRESDEN/oai:qucosa:de:qucosa:32131 |
| Date | 08 November 2018 |
| Creators | Beydeda, Sami, Gruhn, Volker |
| Source Sets | Hochschulschriftenserver (HSSS) der SLUB Dresden |
| Language | English |
| Detected Language | English |
| Type | info:eu-repo/semantics/publishedVersion, doc-type:bookPart, info:eu-repo/semantics/bookPart, doc-type:Text |
| Rights | info:eu-repo/semantics/openAccess |
| Relation | 978-3-540-21871-5 |
Page generated in 0.0023 seconds