Run Settings — Complete Reference

Overview

Run Settings let you define exactly how your test jobs behave — from device preparation and app lifecycle, to retry logic, timeouts, App Vitals monitoring, and post-run integrations. Configure a named Run Setting profile once and apply it across manual sessions, automation jobs, and test suites.

Access: From the Project Dashboard, click the Run Settings icon.

Run Settings Types

RobusTest provides three types of Run Settings, each designed for a specific testing mode:

Framework Applicability Key

Throughout this document, the Applies To column uses these short labels:

All Settings by Category

1. General Settings

Control how the device, app, and environment are prepared before a test begins.

1a. Device & App Preparation

Tip: Combining uninstallAppBeforeRun with deviceReset gives the cleanest possible starting state and is recommended for regression jobs where result consistency matters.

2. Job Settings

Govern the lifecycle of a full test execution — retries, timeouts, device management, and recording.

2a. Retry Behaviour

Tip: Use retryOnSameDevice when failures are likely due to timing or transient issues. Use a different device for retries when you suspect device-specific instability.

2b. Timeouts

Tip: Set testcaseTimeout slightly above your longest expected test case duration to protect jobs from hanging indefinitely on a stuck test.

2c. Device Management

2d. Triggers

3. App Vitals

App Vitals provides deep, app-level health metrics collected in parallel with test execution — with no changes required to your test scripts.

Applies To: Espresso, XCUITest

For a full list of metrics collected per platform see:

• AppVitals Android Metrics Reference
• AppVitals iOS Metrics Reference

4. Hooks

Configure external integrations that are triggered when a job completes. Use these to push job data to monitoring systems or call external endpoints.

4a. REST Webhook

Trigger an external endpoint when the job finishes. Can be used with any REST-compatible service including Slack incoming webhooks.

Applies To: Espresso, XCUITest, Roku

4b. InfluxDB Integration

Push job metrics directly to your InfluxDB instance for custom dashboards and long-term trend analysis.

Applies To: Espresso, XCUITest, Roku

5. Storage Settings

Configure where job artefacts (logs, screenshots, videos) are stored. By default, artefacts are stored in the RobusTest default storage. Use this section to route artefacts to a custom cloud storage engine.

Applies To: Espresso, XCUITest

6. Test Data Collections

Configure what test artefacts are collected and pushed to external integrations (such as Report Portal) at the end of a job run. Each entry in the list defines one artefact type and its destination.

Applies To: Espresso, XCUITest

Invoke Condition fields:

Note: The stats data point is mandatory in at least one entry. Conditions cannot be applied to the stats data point.

For full integration setup see:

• Pushing Data to Report Portal
• Test Data Collection: Report Portal

7. Custom Tags

Tags are labels automatically applied to test case results based on content found in the test output or device log. This lets you categorise failures by type (e.g. "crash", "network error", "timeout") without manual review.

Applies To: Espresso, XCUITest

Example: Create a tag named "Crash Log", searching result for "INSTRUMENTATION_RESULT: shortMsg=Process crashed" with condition true. Any test case whose result contains that string is automatically labelled Crash Log.

8. Analysis Rules

Analysis rules let you define custom conditions that override the default job pass/fail status. Rules are evaluated in order — the first matching rule determines the final job status.

Applies To: Espresso, XCUITest

Example: Set job status to Pass if at least 95% of test cases pass — even if a small number of known flaky tests fail. Set Git PR state to success so your CI pipeline proceeds.

9. Screenshot Settings

Control when screenshots are automatically captured and how many are saved per test case.

Applies To: Espresso, XCUITest

Tip: For failure investigation, use ending capture limit — you get the screenshots closest to the point of failure, which are the most useful for debugging.

Default Values Quick Reference

Applying Run Settings

Manual Test Session

1. Click the Manual icon on the Project Dashboard.
2. Select your device from the device list.
3. Click the Configure Session icon (top-right).
4. Choose your Run Setting profile from the Run Settings dropdown.
5. Click the info icon next to the selected profile to review its configuration.
6. Start the session.

Automation Job (Hub)

1. Click the Automation icon on the Project Dashboard.
2. Select one or more devices.
3. Click Configure Session (top-right).
4. Select your Run Setting profile from the dropdown.
5. Review and confirm, then launch the job.

Test Suite (Runner)

1. Click the Test Suites icon on the Project Dashboard.
2. Locate the test suite you want to run.
3. Click the Play icon next to the suite.
4. Select your Run Setting profile from the dropdown.
5. Confirm and execute.

All Attributes at a Glance

Related Documentation

• AppVitals Android Metrics Reference
• AppVitals iOS Metrics Reference
• Manual Session
• Multi-Device Testing
• Automation Reports
• Pushing Data to Report Portal
• Test Data Collection: Report Portal
• FAQ