|User Guide / Getting started|
The basic TestArchitect infrastructure includes Repository Server, License Server, client machines, and execution machines.
|Repository Server||The component responsible for managing one or more TestArchitect repositories. Each repository holds the test assets for one or more of your test projects. You can choose to have a repository server running on your local machine, along with TestArchitect Client. You may also connect to repositories hosted on other machines on your network, possibly including machines dedicated to hosting TestArchitect repositories.|
|License Server||Responsible for issuing licenses to your client machines and test
controllers. You can manage your purchased licenses using this tool's control
Note: It is possible to set up a Redundant License Server, which is highly desirable in the event that the primary license server, for whatever reason, becomes unavailable.
|Client machine||A workstation having TestArchitect Client installed, from which you can author tests, direct the execution of tests, generate reports, etc.|
Real or virtual machine which has TestArchitect Controller and necessary automation libraries installed, and which can be used to execute tests, either locally or on attached mobile devices.Note that any client machine (with TestArchitect Client installed) also has TestArchitect Controller installed, and so can be used to execute tests. Tests can also be executed on remote machines.