Reducing complexity of data flow testing in the verification of a IEC-62304 flexible workflow system
SAFECOMP'11 Proceedings of the 30th international conference on Computer safety, reliability, and security
A test case refactoring approach for pattern-based software development
Software Quality Control
A multiple case study of design pattern decay, grime, and rot in evolving software systems
Software Quality Control
Design pattern alternatives: what to do when a GoF pattern fails
Proceedings of the 17th Panhellenic Conference on Informatics
| Hi-index | 0.00 |
Design-for-testability is a very important issue in software engineering.It becomes crucial inthe case of OO designs where control flows are generally not hierarchical, but are diffuse and distributed over the whole architecture.We introduce the concept of a "testing conflict" when potentially concurrent client/supplier relationships between the same classes along different paths exist in a system.Such conflicts may be hard to test, especially when dynamic binding and polymorphism are involved.We describe the conflicts using topological classconfiguration diagrams.An overall architecture is represented as a combination of the initial design and several patterns.We focus on the design patterns as coherent subsets in the architecture, and we explain how their use can provide a way for limiting the complexity oftesting for conflicts, and of confining their effects to the classes involved in the pattern.