Difference between revisions of "Old GXtest Installation guide"

From GXtest Wiki
Jump to: navigation, search
(Página nueva: categoría:Installation Guides The various components to install are listed below: * GXtest Designer Installation Guide * GXtest Recorder Installation Guide * [[GXtest Ma...)
 
Line 8: Line 8:
 
** [[GXtest Manager Installation Guide#GXtest_Executor|GXtest Executor Installation Guide]]
 
** [[GXtest Manager Installation Guide#GXtest_Executor|GXtest Executor Installation Guide]]
  
GXtest Designer se instalará en las máquinas donde los usuarios quieran modelar sus casos de prueba. Es un componente monousuario que se conecta a su propia base de datos y luego a la base de datos del Manager, por lo que debe estar en la misma LAN.
+
GXtest Designer has to be installed on machines where users want to model the test cases. It is a single-user component that connects to its own database and then the Manager database, so it must be on the same LAN.
  
Adicionalmente, en donde se instale un GXtest Designer es necesario instalar el compoente GXtest Recorder para poder grabar los casos de prueba desde el Internet Explorer.
+
Additionally, where installing a GXtest Designer you need to install GXtest Recorder to record test cases from Internet Explorer.
  
El componente GXtest Recorder puede ser instalado sin el GXtest Designer, a modo de grabar casos de prueba y guardarlos como archivos XML comprimidos, que pueden ser enviados luego al usuario de GXtest Designer, para que los importe y utilice en algún proyecto.
+
The component GXtest Recorder can be installed without the GXtest Designer, in order to record test cases and save them as compressed XML files that can be sent after to the user who is using GXtest Designer, to import and use them in any project.
  
 +
The GXtest Manager is installed as Web application in a .NET environment. It can be remotely accessed by different users. At the same server (not necessarily) GXtest Daemon component must be running, which checks if there are scheduled tasks ready to execute, and makes them execute in the indicated  machine (in the GXtest Executor component).
  
El GXtest Manager se instala como aplicación Web en ambiente .NET. Puede ser accedido por distintos usuarios en forma remota. En el mismo servidor (no necesariamente) debe estar corriendo el componente GXtest Daemon que se encarga de verificar si hay tareas agendadas listas para ejecutar, y las manda a ejecutar cuando corresponda a la máquina indicada (al componente GXtest Executor).
+
So there can be several GXtest Executor where tests are run effectively. They must also have access to the GXtest Manager database. Because they are the ones who run the test cases, they must also have access to the application under test.
 
+
Entonces, pueden haber varios GXtest Executor donde efectivamente se ejecutan las pruebas. Estos deben tener acceso también a la base de datos del GXtest Manager. Como son los que ejecutan deben tener acceso también a la aplicación bajo pruebas.
+

Revision as of 14:29, 11 December 2009

categoría:Installation Guides

The various components to install are listed below:

GXtest Designer has to be installed on machines where users want to model the test cases. It is a single-user component that connects to its own database and then the Manager database, so it must be on the same LAN.

Additionally, where installing a GXtest Designer you need to install GXtest Recorder to record test cases from Internet Explorer.

The component GXtest Recorder can be installed without the GXtest Designer, in order to record test cases and save them as compressed XML files that can be sent after to the user who is using GXtest Designer, to import and use them in any project.

The GXtest Manager is installed as Web application in a .NET environment. It can be remotely accessed by different users. At the same server (not necessarily) GXtest Daemon component must be running, which checks if there are scheduled tasks ready to execute, and makes them execute in the indicated machine (in the GXtest Executor component).

So there can be several GXtest Executor where tests are run effectively. They must also have access to the GXtest Manager database. Because they are the ones who run the test cases, they must also have access to the application under test.