Run Settings

⚙️ Run Settings Overview

Customize Your Test Execution Environment

Run Settings provide powerful customization capabilities for your test sessions. Whether you’re conducting manual testing or running automation suites, Run Settings allow you to define and control the behavior, configuration, and environment of your test executions.

🎯 Purpose & Benefits

Why Use Run Settings?

• Standardize test execution environments

• Ensure consistent testing configurations

• Customize behavior for different test scenarios

• Optimize test performance and reliability

🚀 Quick Access

Getting Started

• Access via ‘Run Settings’ icon on Project Dashboard

• Create multiple configurations for different needs

• Apply settings to manual and automation sessions

• Share configurations across team members

Overview

Whenever you start a new test session - whether Manual or Automation - there are certain default configuration values that determine how your test session behaves. Run Settings enable you to customize these default configuration values to meet your specific testing requirements.

Run Settings Types

🎯 Four Specialized Configuration Types

RobusTest offers four distinct Run Settings types, each optimized for specific testing scenarios and frameworks.

📱 Manual Run Settings

Interactive Testing Configuration

Configure settings for manual test sessions including device interaction, session behavior, and user interface preferences.

Best for: Exploratory testing, usability validation

Manual Run Setting

🤖 Automator Run Settings

Automation Framework Configuration

Customize automation execution parameters, timeout values, and framework-specific behaviors for optimal test performance.

Best for: Appium, Selenium automation scripts

RobusTest Automator Run Setting

🏃 Runner Run Settings

Test Suite Execution Configuration

Define execution strategies, parallel processing options, and reporting configurations for comprehensive test suite runs.

Best for: Large-scale test execution, CI/CD integration

RobusTest Runner Run Settings

☕ Espresso Run Settings

Android Native Testing Configuration

Specialized settings for Espresso framework testing including Android-specific configurations and instrumentation options.

Best for: Android native app testing

Espresso Run Settings

Run Setting Attributes Reference

This comprehensive table lists all available run setting attributes and their descriptions for configuring test execution environments.

Run Setting Attributes

setting name	desc
pagesourceTimeout	“time (in secs) system should wait for pagesource”
recordingMode	“mode in which RobusTest automator creator session should start. Values - automation, automationAdvance, manual”
streamPagesource	“should the pagesource stream periodically or on demand. Values - true, false”
enterTextMethod	“method for entering values in text fields. Values - appium,robusest,adb for android | appium for iOS”
waitforElement	“time (in secs) system should look for an element”
checkElementIsVisible	“verify if element is visible before interacting with it”
handleAndroidPermissionPopup	“method for handling permission pop ups in Android. Values- allow, deny, null”
deviceReset	“should the device be reset at the start and end of test session”
uninstallAppAfterRun	“should the app under test be uninstalled after test session”
uninstallAppBeforeRun	“should the app under test be uninstalled before test session”
	“JOB”
maxJobAttempts	“number of times job should be attempted”
maxTestCaseAttempts	“number of times a failed test case should be attempted”
addMoreDevices	“should system enable addition of devices once test run has started. if true, devices may be added even beyond maxDeviceCount”
retryOnSameDevice	“should a failed test case be retried on the same device”
testcaseTimeout	“maximum time (secs) for a test case to run”
devicePreparationTimeout	“time (in secs) allowed for device preparation before test execution”
tags	“generate custom tags for a test case result based on log content”
	“name for the tag”
	“source to look for search term. Values - result, deviceLog”
	“term to search for”
	“look for the presence or absence of the search term. Values - true, false”
analysis	“set job pass or fail status based on custom logic; multiple conditions are applied in order”
	“name for the entry”
	“source to consider for creating the condition. Values - job, tag”
	“attribute to consider when calcalating. Values - pass, fail, error”
	“metric to consider when calculating. Values - %, count”
	“threshold to compare with when comparing”
	“should the job status be changed based on the condition”
	“value for status of the job”
	“value to be set for the associated Git pull request. Values - failure, success”
	“status of the job for email. Values - pass, fail”
runTimeout	“time (in secs) the job can be in running state before being discarded”
queueTimeout	“time (in secs) the job should wait in the queue before being discarded”
limitToMaxDevice	“should the number of devices be limited to maxDeviceCount”
firstRetryOnSameDevice	“retry the first attempt after a failure on the same device”
	“UNINSTALL APPS”
uninstallApps	“comma separated list of app packages to uninstall before running job”
	“PERFORMANCE”
monitor	“should the system monitor performance”
saveData	“should the performance data be saved in RobusTest”
params	“additional performance monitoring parameters (key-value pairs)”
	“HOOKS”
influxDB	“influxDB Host”
	“influxDB Database Name”
	“influxDB Username”
	“influxDB Password”
email	“Email addresses to notify when job completes”
	“Email addresses to notify when job fails”
	“Email addresses to notify when job passes”
rest	“URL for the listener”
	“HTTP Method to be used”
	“Authtoken, if any”

Configuring Run Settings

🔧 Configuration Workflow

After creating a run setting, you can apply it to different types of test sessions. Each session type has its own configuration pathway.

📱 Manual Test Sessions🤖 Automation Test Sessions🏃 Test Suite Execution

Applying Run Settings to Manual Testing

Configure your manual test sessions with custom run settings for optimal testing experience.

🎯 Step-by-Step Configuration

Manual Session Setup Process

1️⃣ Access Manual Testing

Start Manual Session

• Click the ‘Manual’ icon on Project Dashboard

• Device selection screen appears

• Ready for configuration

2️⃣ Configure Session

Apply Run Settings

• Click ‘Configure Session’ icon (top right)

• Select from ‘Run Settings’ dropdown

• View configuration details via info icon

🚀 Best Practices & Tips

Optimize Your Run Settings Usage

💡 Pro Tips

Maximize Run Settings Effectiveness:

• Create specific settings for different testing phases (smoke, regression, performance)

• Use descriptive names for easy identification

• Regularly review and update settings based on project evolution

• Share standardized settings across team members for consistency

📋 Organization

Settings Management

• Use clear naming conventions

• Group settings by test type

• Document configuration purposes

• Version control settings changes

🔄 Maintenance

Keep Settings Updated

• Review settings regularly

• Update for new features

• Remove obsolete configurations

• Test settings before deployment

👥 Collaboration

Team Coordination

• Share settings across projects

• Standardize team configurations

• Document setting purposes

• Train team on usage patterns