Difference between revisions of "GXtest Executor User's Manual"
(→Setting GXtest Executor) |
|||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Idiomas| Manual de Usuario de GXtest Executor| GXtest Executor User's Manual | GXtest Executor ユーザーズマニュアル}} | ||
[[Category:GXtest Guides]] | [[Category:GXtest Guides]] | ||
== Setting GXtest Executor == | == Setting GXtest Executor == | ||
| − | Basically an Executor is a component that is "listening" to execute tests on the machine where it is installed. Once it is notified from the Manager that it is time to run a particular test, it starts to run those test cases, opening the browser for this. | + | Basically an Executor is a component that is "listening" to execute tests on the machine where it is installed. Once it is notified from the Manager that it is time to run a particular test, it starts to run those test cases, opening the browser for this. To optimize execution time, if GXtest Executor is idle, it starts executing tasks up to two minutes before the task execution start time. |
| + | |||
| + | The application who connects with Executor to indicate it to start is GXtest Manager with the component GXtest Daemon (GXtest Daemon.exe). | ||
Then, the Executor connects to the database to know the details of the test to run, using the connection data that GXtest Manager gave him when indicated to start running. | Then, the Executor connects to the database to know the details of the test to run, using the connection data that GXtest Manager gave him when indicated to start running. | ||
| Line 10: | Line 13: | ||
== Command Line Execution == | == Command Line Execution == | ||
| − | The component to be used from GXtest Manager to run the tests is available to run | + | The component to be used from GXtest Manager to run the tests (GXtest Daemon) is available to run from any external application. With it, you can start an execution of a test suite in any Executor available. This can be invoked by command line, and this runs a Test Case, or a Task, and saves a file containing the result of the test. |
<pre> | <pre> | ||
| Line 18: | Line 21: | ||
For example, run: | For example, run: | ||
| − | cd | + | cd "C:\Program Files\Abstracta\GXtest Daemon" <br> |
| − | GXtestDaemon.exe 1 1 c:\temp | + | GXtestDaemon.exe 1 1 "c:\temp" |
Here, taskId = 1, and TaskInstance = 1 (task instance number must be different on each execution for each task) | Here, taskId = 1, and TaskInstance = 1 (task instance number must be different on each execution for each task) | ||
| − | The Executor executes the test cases and stores in the path at least 2 files: | + | The Executor executes the test cases and stores in the path at least 2 files, with a copy of the results: |
# tc1.xml | # tc1.xml | ||
# tc1_detailed.xml | # tc1_detailed.xml | ||
| − | The first one simply says if it failed or passed for each step. If some mistake were made, each command will have an "Error Detail. Additionally, on error, there are attached the response html of the application and also the screenshot of the browser. You can see all this more detailed (parameters, input data, execution times, etc..) in the detailed file (tc1_detailed.xml). | + | The first one simply says if it failed or passed for each step. If some mistake were made, each command will have an "Error Detail". Additionally, on error, there are attached the response html of the application and also the screenshot of the browser. You can see all this more detailed (parameters, input data, execution times, etc..) in the detailed file (tc1_detailed.xml). |
| + | |||
| + | You can also search execution results in GXtest Manager. | ||
| − | An important difference to consider whether to run a Task and a Test Case is that when running a Test Case results are stored in XML files as explained above, and if you run a Task results are stored in the GXtest Manager database | + | An important difference to consider whether to run a Task and a Test Case is that when running a Test Case results are stored in XML files as explained above, and if you run a Task, results are stored in the GXtest Manager database too. In addition, the Task specified must be valid to run (for example, the specified instance of the task must not have been executed). |
Latest revision as of 17:17, 4 October 2017
 |
 |
 |
Setting GXtest Executor
Basically an Executor is a component that is "listening" to execute tests on the machine where it is installed. Once it is notified from the Manager that it is time to run a particular test, it starts to run those test cases, opening the browser for this. To optimize execution time, if GXtest Executor is idle, it starts executing tasks up to two minutes before the task execution start time.
The application who connects with Executor to indicate it to start is GXtest Manager with the component GXtest Daemon (GXtest Daemon.exe).
Then, the Executor connects to the database to know the details of the test to run, using the connection data that GXtest Manager gave him when indicated to start running.
So, the main consideration in GXtest Executor is the port where is listening. To configure it you must double-click the icon in the System Tray and then enter the port number. The default is 6681. From that icon, you can also access to the log file.
Command Line Execution
The component to be used from GXtest Manager to run the tests (GXtest Daemon) is available to run from any external application. With it, you can start an execution of a test suite in any Executor available. This can be invoked by command line, and this runs a Test Case, or a Task, and saves a file containing the result of the test.
GXtestDaemon.exe {TaskId TaskInstance Path {-v VAR_1 VALUE_1 VAR_2 VALUE_2 ... }} | {ProjectName TestCaseName OutputPath ExecutorIP ExecutorPort}
For example, run:
cd "C:\Program Files\Abstracta\GXtest Daemon"
GXtestDaemon.exe 1 1 "c:\temp"
Here, taskId = 1, and TaskInstance = 1 (task instance number must be different on each execution for each task)
The Executor executes the test cases and stores in the path at least 2 files, with a copy of the results:
- tc1.xml
- tc1_detailed.xml
The first one simply says if it failed or passed for each step. If some mistake were made, each command will have an "Error Detail". Additionally, on error, there are attached the response html of the application and also the screenshot of the browser. You can see all this more detailed (parameters, input data, execution times, etc..) in the detailed file (tc1_detailed.xml).
You can also search execution results in GXtest Manager.
An important difference to consider whether to run a Task and a Test Case is that when running a Test Case results are stored in XML files as explained above, and if you run a Task, results are stored in the GXtest Manager database too. In addition, the Task specified must be valid to run (for example, the specified instance of the task must not have been executed).
