Configuring Workflows

​

Accessing Workflow Configuration

1. Go to Workflows in the sidebar
2. Click on a workflow card to open its details page
3. Click the Configuration tab

​

Workflow Details Page

​

Header Information

• Workflow Name - with options to:
  • 📋 Copy workflow ID
  • ✏️ Rename workflow
• Run Now button - Execute the workflow immediately
• Metadata: Tests count, Created date, Current Status

​

Summary Statistics

• Total Executions - Number of times the workflow has run
• Successful Runs - Count of successful executions
• Failed Runs - Count of failed executions
• Avg Success Rate - Percentage of successful runs

​

Tabs

• History - View past workflow executions and results
• Configuration - Manage tests and settings (covered in this guide)

​

Managing Tests in a Workflow

​

Adding Tests

1. Use the Search box to find tests by name
2. Apply filters:
   • All Builds - Filter by specific build
   • All Platform - Filter by Android or iOS
   • All Tags - Filter by test tags
3. Check the checkbox next to tests you want to add
4. Tests are automatically added to the workflow

​

Removing Tests

1. Find the test in the selected tests list
2. Uncheck the checkbox next to the test name
3. The test is immediately removed from the workflow

​

Viewing Test Details

• Test name
• Platform icon (Android/iOS)
• Build name (e.g., “Android Test App”)
• Step count (e.g., “2 steps”)
• Expand arrow (>) to view test steps

​

Test Filters

Search: "login"
Platform: Android
Tags: "smoke-test"

​

Workflow Settings

​

Renaming a Workflow

1. Click the Rename button (✏️) next to the workflow name
2. Enter the new name
3. Save

​

Copying Workflow ID

• API integrations
• CI/CD pipelines
• Support requests

​

Workflow Overrides

​

Build Override

• Run all tests against a specific build version
• Test a staging build without changing each test’s configuration
• A/B test different build versions

1. Open the workflow’s Configuration tab
2. Find the Build Override section
3. Select a build from the dropdown
4. All tests in this workflow will now use the selected build instead of their individual build settings

​

Location Override

• Test location-based features at a specific location
• Ensure consistent location for all tests in a workflow
• Test geofencing or regional features

1. Open the workflow’s Configuration tab
2. Find the Initial Location section
3. Enter Latitude and Longitude coordinates
4. All tests will start with the device at this location

​

Integrations

​

Slack Integration

1. Click Slack button
2. Follow the integration flow
3. Choose which Slack channel to send notifications to
4. Select a notification rule:
   • On Start (workflow started)
   • On Success (workflow completed successfully)
   • On Failure (workflow failed)

​

Other Integrations

​

Execution History

• All past runs of the workflow
• Execution status (Passed, Failed, Running)
• Timestamp of when it ran
• Detailed test results for each run

​

Manual Execution

1. Go to Workflows page
2. Click the Run button (▶) on the workflow card

1. Open the workflow details page
2. Click Run Now button in the top-right

​

Execution Process

1. All selected tests are queued for execution
2. Tests run concurrently (subject to device availability and plan limits)
3. Each test runs its steps independently
4. Results are collected and aggregated
5. Workflow status is updated (Passed/Failed) once all tests finish

​

Monitoring Execution

• Status shows as “Running” 🟡
• You can view progress in the History tab
• Individual test results appear as tests complete

​

Workflow Execution Behavior

​

Test Execution Order

​

What Happens When a Test Fails?

• ❌ The failed test is marked as “Failed”
• ✅ The workflow continues executing remaining tests
• ⚠️ The overall workflow status becomes “Failed”
• 📊 You can view failure details in the History tab

​

Best Practices

​

Keep Tests Up to Date

• Remove tests that are no longer relevant
• Update test names when features change
• Regularly review and clean up test selections

​

Organize by Purpose

• “Login Flow” - All authentication tests
• “Smoke Tests” - Critical path only
• “Full Regression” - Comprehensive coverage

​

Monitor Workflow Health

• Check the Avg Success Rate metric
• Investigate failing tests promptly
• Review execution history regularly
• Set up Slack notifications to get alerts

​

Next Steps