The Test Bus Imperative: Architectures That Support Automated Acceptance Testing

Authors:
Robert C. Martin
Affiliations:
Object Mentor
Venue:
IEEE Software
Year:
2005

Citing 3
Cited 2

Object-oriented software engineering

Object-oriented software engineering
Test Driven Development: By Example

Test Driven Development: By Example
Patterns of Enterprise Application Architecture

Patterns of Enterprise Application Architecture

Towards traceable test-driven development

TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
ADAM: External dependency-driven architecture discovery and analysis of quality attributes

ACM Transactions on Software Engineering and Methodology (TOSEM)

Quantified Score

Hi-index	0.00

Visualization

Abstract

Agile methods--more specifically, test-driven development practices1--have begun to raise the software industry's awareness of automated acceptance testing. We now recognize that armies of manual testers slogging through reams of tedious manually executed test scripts, under schedule pressure at the end of a release, don't ensure quality. Consequently, software producers have started architecting their software systems with built-in test busses. However, setting up automated acceptance testing requires at least three major architectural separations.