Docs

Report Portal Integration

RobusTest integrates with Report Portal to push test artefacts — results, logs, and screenshots — from your job runs. The integration is set up once by an administrator in the Admin Console. The resulting Integration ID is then used in Run Settings to configure what gets pushed, and under what conditions.

Setting Up in Admin Console

  1. Go to Admin Console → Integrations.
  2. Click the + button to create a new integration.
  3. Fill in the following:
    • Name — a label for this integration
    • Service — select Report Portal
    • Base URL — your Report Portal API URL in the format http://<Report Portal URL>/api/v1
    • Auth Token — your Report Portal authentication token
  4. Click Save.

If the connection is successful, RobusTest will validate the URL and token against your Report Portal instance.

Once saved, the integration appears in Admin Console → Integrations with its Integration ID. Copy this ID — it is required when configuring Run Settings.

Test Data Collection Entries

RobusTest pushes artefacts to Report Portal at the end of a job run. Each artefact type is configured as a separate Test Data Collection entry in your Run Setting — one entry per artefact type.

Each entry takes three required fields.

testDataCollections.integrationType

Enter reportPortal.

testDataCollections.integrationID

Enter the Integration ID of your Report Portal integration from Admin Console → Integrations.

testDataCollections.testDataPoint

Determines what is pushed to Report Portal. Valid values:

Value What is pushed
stats Test case results — pass/fail counts, job start/end times, duration, test case list. Mandatory — at least one entry must have this value, or no data is pushed at all.
frameworkLog Framework logs from the test runner (Espresso, Appium, XCUITest, etc.)
screenshot Screenshots captured during the job

Conditional Sending

For frameworkLog and screenshot, you can push data conditionally based on test case result attributes.

To set a condition:

  1. In the Invoke Conditions section of a test data collection entry, click the + icon.
  2. A condition entry appears. Expand it and fill in:
    • attributeName — the attribute to evaluate (e.g. status)
    • attributeValue — the value to match (e.g. Fail, Pass)
    • operator — the comparison operator (e.g. =)

You can set multiple conditions per entry. Conditions cannot be applied to stats entries.

Example

Send framework logs only for failed test cases and screenshots only for passed test cases:

Test Data Collection testDataPoint Condition
Entry 1 stats (none — required)
Entry 2 frameworkLog status = Fail
Entry 3 screenshot status = Pass