Difference between revisions of "GXtest Daemon User's Manual"
(Página nueva: Categoría: GXtest Guides GXtest Manager permite agendar las tareas en las cuales se ejecutarán los conjuntos de casos de prueba. Para brindar mayor flexibilidad a la ejecució...) |
|||
| Line 1: | Line 1: | ||
[[Categoría: GXtest Guides]] | [[Categoría: GXtest Guides]] | ||
| − | + | GXtest Manager allows you to schedule the tasks which will run the test case sets. For greater flexibility in execution is that there GXtest Executor and GXtest Daemon components. The Executor is the engine that actually runs the tests and record the results in the database. Of these components could be multiple distributed instances. The Daemon is the component that allows GXtest Manager to communicate with the various Executors. | |
| − | GXtest Manager | + | |
== GXtest Daemon == | == GXtest Daemon == | ||
| − | + | It installs as a Windows service, generally on the same machine where GXtest Manager is installed, but this is not a constraint. It is necessary to properly configure the Daemon to allow it to access to the database (String connection and authentication). | |
| − | + | This component will be checking for Tasks to be performed (it monitors the database every 1 minute). If there is some pending task to run, the Daemon invokes the corresponding Executor giving it the ''remote'' Connection String. This provides the convenience of not having to configure each Executor after every configuration change to access to the database. Instead of that, this task is made centrally. | |
== GXtest Executor == | == GXtest Executor == | ||
| − | + | It installs as an application that starts with the system and running on the System Tray. From there we can access its settings (port where is listening). This will actually run the tests and record the results in the database. | |
| − | + | Then we should set it up in GXtest Manager, indicating a name, IP and port where the Executor listens. We will also configure which version of browser and operating system that machine has, in order to register this information. | |
=== See Also === | === See Also === | ||
| − | * [[ | + | * [[GXtest_Manager_User's_Manual#Executors |How to configure the Executors in GXtest Manager]] |
| − | * [[ | + | * [[GXtest Executor User's Manual (command line)]] |
Revision as of 20:04, 19 December 2009
GXtest Manager allows you to schedule the tasks which will run the test case sets. For greater flexibility in execution is that there GXtest Executor and GXtest Daemon components. The Executor is the engine that actually runs the tests and record the results in the database. Of these components could be multiple distributed instances. The Daemon is the component that allows GXtest Manager to communicate with the various Executors.
GXtest Daemon
It installs as a Windows service, generally on the same machine where GXtest Manager is installed, but this is not a constraint. It is necessary to properly configure the Daemon to allow it to access to the database (String connection and authentication).
This component will be checking for Tasks to be performed (it monitors the database every 1 minute). If there is some pending task to run, the Daemon invokes the corresponding Executor giving it the remote Connection String. This provides the convenience of not having to configure each Executor after every configuration change to access to the database. Instead of that, this task is made centrally.
GXtest Executor
It installs as an application that starts with the system and running on the System Tray. From there we can access its settings (port where is listening). This will actually run the tests and record the results in the database.
Then we should set it up in GXtest Manager, indicating a name, IP and port where the Executor listens. We will also configure which version of browser and operating system that machine has, in order to register this information.
