Get test job results
To view results of a test job run, you can either use the web interface of TestEngine or send a request to the TestEngine API using curl, ReadyAPI, or any other similar tool.
Using API
Get an overview of test jobs in TestEngine
Use the following operation:
Authentication
The request must be authenticated by a TestEngine user.
Note: | If you authenticate as a non-admin user, you will be able to view only those reports on test jobs that you have started. If you authenticate as an administrator, you will be able to view all the test jobs in TestEngine. |
Get a full report on a test job
Use the following operation:
Authentication
The request must be authenticated by a TestEngine user.
Note: | Results that you see depend on the authentication. If you authenticate as a user, you will see only the test jobs started by that user; if you authenticate as an administrator, you will see all the test jobs in TestEngine. |
Headers
Header | Description |
---|---|
Accept |
Specifies the format of the report. Possible values:
If the header is not set explicitly, a JSON report will be returned. |
Using Web UI
To see test job results, go to the home page of TestEngine:
For example, if TestEngine is installed on your local machine and you run it on the default port, use the following link:
The Overview page of the TestEngine web interface contains a list of existing test jobs:
Tip: | You can filter test jobs by a name, status, used tags, and the user who has sent the job. Besides that, you can search for a specific test job by a string included in its project, author, status, type, or tag. |
The table contains brief information on test jobs:
Column | Description | ||
---|---|---|---|
Project | The name of the project to run. | ||
Status | Current state of a test job. Possible statuses: QUEUED, RUNNING, CANCELED, FAILED, FINISHED. |
||
Author | The name of the user, who sent the test job to TestEngine. Administrators can examine test jobs created by other users. |
||
Test Type |
Shows whether the test job is a functional test or security test.
|
||
Tags |
Shows which tags were used to run the test job. |
||
Submitted | A timestamp when the test job was sent to TestEngine. | ||
Run Time | The time of the test run. | ||
Queue Time | How much time the test was in the queue. | ||
Total Time | The total time of the test run, including the time in the queue. | ||
![]() |
Cancel the test job. | ||
![]() |
Get the test job ID. | ||
![]() |
Download the test job report in the JSON, JUnit XML, Excel or PDF format. |
Get transaction report
A transaction report is a JSON file that contains full information on HTTP transactions that took place during a test job run. Transactions are logged only for request test steps, such as SOAP Request, REST Request, and so on.
Get a report on all the transactions within a test job
Use the following operation:
Authentication
The request must be authenticated by a TestEngine user.
Note: | Results that you see depend on the authentication. A user can see only the transactions of test jobs that they have started; an administrator can see transactions of all the jobs in TestEngine. |
Get a transaction report for a particular transaction
Use the following operation:
Authentication
The request must be authenticated by a TestEngine user.
Note: | Results that you see depend on the authentication. A user can see only the transactions of test jobs that they have started; an administrator can see transactions of all the jobs in TestEngine. |
The address and port of your TestEngine installation.
The address and port of your TestEngine installation.
The id of the job. The id is included in the response that you receive when starting the job. Alternatively, you can click in the Web UI, or get an overview of test jobs and find the id of the needed job there.
The address and port of your TestEngine installation.
The id of the job. The id is included in the response that you receive when starting the job. Alternatively, you can click in the Web UI, or get an overview of test jobs and find the id of the needed job there.
The address and port of your TestEngine installation.
The id of the job. The id is included in the response that you receive when starting the job. Alternatively, you can click in the Web UI, or get an overview of test jobs and find the id of the needed job there.