Artifact: Test Automation Architecture |
This artifact specifies various test automation design and implementation elements that embody the fundamental characteristics of the test automation software system.
Purpose
To provide a means of reasoning about, managing, and communicating the fundamental characteristics of the test-automation software system.
Relationships
Container Artifact | Test Architecture
Roles | Responsible: | Modified By: Test Designer
Tasks | Input To: Define Testability Elements Identify Testability Mechanisms Structure Test Environment Configuration | Output From: Define Testability Elements Define Test Strategy Identify Testability Mechanisms
Description
Main Description | The Test Automation Architecture provides a comprehensive architectural overview of the test-automation system, using a number of different architectural views to depict different aspects of the system. It serves as a means of reasoning about, managing, and communicating the fundamental characteristics and features of the test-automation software system. It provides a governing focus for the test-automation software that enables the required system to be realized in respect to key aspects such as: maintainability, extensibility, reliability, concurrency, distribution, security, and recovery.
Tailoring
Impact of not having | For larger test organizations, not capturing the test automation architecture may lead to: Less efficiency in using the test resources Overlaps in developing automated tests Maintenance issues over a longer period of time
Reasons for not needing | Recommended on projects where the test architecture is relatively complex, when a large number of staff members will be collaborating on building automated tests, or when the test automation system is expected to be maintained over a long period of time. In some cases, this might simply be a whiteboard diagram that is recorded centrally for interested parties to consult.
Representation Options | UML Representation: Some aspects of the Test Automation Architecture can optionally be described using a UML model, stereotyped as <<test automation architecture>>. Where available, you may be able to make use of some part of the existing Test Automation Architectures with little need to tailor them. However, usually each project requires some variation in approach, techniques, and tools, which ultimately affects the Test Automation Architecture itself. In many cases, tailoring or creating an appropriate Test Automation Architecture will occur during the Elaboration phase, and will be fine-tuned and extended with each subsequent iteration (in both the Construction and Transition phases). For the definition of Test Automation Architecture, it can be helpful to use a single source that maintains an outline description of the main characteristics of the architecture. As an alternative to formal documentation, you may choose to simply record this information as a set of informal architectural notes accompanied by a minimal set of explanatory diagrams, possibly maintained on a white-board readily visible to the test team.
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.