Reg. Scheduling from TestOops

Web Testing
3

:clipboard: Step-by-Step Guide to Scheduling Test Runs in TestOps

Prerequisites

Before you start scheduling, make sure you have:

  • :white_check_mark: A test environment configured (Local, TestCloud, or Docker)
  • :white_check_mark: Your test scripts uploaded to a Git repository linked with TestOps
  • :white_check_mark: Katalon TestOps Agent installed (if using local/on-premises execution)

Main Steps to Schedule a Test Run

Step 1: Navigate to Executions

  1. Go to your Project in Katalon TestOps
  2. Click on the Executions tab
  3. Click + Create button

Step 2: Choose Execution Type

Select one of the following:

  • Create Automated Test Run - For automated test suites (recommended for scheduling)
  • Create Manual Test Run - For manual testing scenarios
  • Create Test Plan - For organizing multiple test runs

Step 3: Configure Your Test Run

  1. Select Script Repository - Choose your Git repository containing test scripts
  2. Choose Test Suite/Collection - Select which tests to run
  3. Select Execution Profile - Pick the appropriate test data profile
  4. Choose Execution Environment - Select from:
    • TestCloud (cloud-based browsers)
    • Local Test Environment (your machine)
    • Docker Environment (containerized execution)
    • Kubernetes (for enterprise deployments)

Step 4: Set the Schedule

  1. Click on the Schedule section
  2. Define your schedule:
    • One-time execution - Run once at a specific date/time
    • Recurring execution - Set daily, weekly, or monthly intervals
  3. Set the Start Date & Time
  4. (Optional) Set an End Date for recurring schedules

Step 5: Advanced Settings (Optional)

  1. Click Advanced settings at the bottom left
  2. Configure additional options like:
    • Retry policies
    • Timeout settings
    • Notification preferences
    • Parallel execution limits

Step 6: Save or Execute

  • Save Configuration - Save without running (for later execution)
  • Schedule & Run - Save and execute immediately

Key Considerations

Aspect Details
Test Environment Must be created and active before scheduling
Git Repository Your test scripts must be in a Git repository linked to TestOps
Execution Modes UI Mode (visual) or Command Line Mode (headless)
TestCloud Tunnel Use for testing private/local applications securely
Automatic Retry Configure in Advanced settings for failed test recovery

References