Customers often ask “Where do we Start” when setting up and configuring their DevTest architecture. Of course, this really depends on how they plan to use DevTest - whether using Virtual Services or running tests or maybe a combination of both. So based on potential usage of DevTest, we started building a Best Practice Architecture Guide based on real world deployments. As a part of this initiative, we will build out several architectures that are implemented by either customers or CA Services or are new/tested architectures that fit a specific need.
Our intention is to provide options for customers, partners and CA Services on how to implement DevTest within their environment to meet the specific use cases.
This document contains the list of DevTest architecture suggestions we plan to implement and to verify in detail.
All DevTest server installations are distributed. All DevTest installations have a SCM repository server attached to store project specific artifacts (test cases, virtual services) and their versions.
- Hybrid environment (on premise and public cloud) – server components are installed in the cloud, except for the Enterprise Dashboard service.
- Everything Cloud (public cloud) – all server components are installed in the cloud
- Multiple Teams – multiple DevTest server installations in the cloud
- Large Team – single DevTest server installation with multiple VSEs and Simulators for load balancing
- Shared DevTest Infrastructure – DevTest server installation for use by internal and external clients
Please let us (Koustubh.Warty, Ulrich_Vogt) know if you want us to cover additional/different architectures.
So far following detailed DevTest Architecture Best Practice Guides have been published: