Test Operation

Estimated reading: 2 minutes

Test Operation is a Designer-level control for running and validating test cases in the CloudTestr environment before proceeding with the standard publishing workflow.

When Test Mode is enabled, publish operations are routed to CloudTestr, where test cases can be added to an execution queue and processed sequentially in the configured order.

Important: Changes to Test Operation take effect immediately. Avoid changing the execution mode while test cases are running or queued, as this may affect their execution.

Test Operation Panel

The Test Operation panel provides a centralized view of the current execution mode and system state.

Element Description
Execution Mode Determines whether publish operations use the standard publishing workflow or Test Mode.
Current Status Displays whether Test Mode is currently Enabled or Disabled.

Execution Modes

Disabled: When Test Mode is disabled, publish operations follow the standard publishing workflow, test execution routing is not applied, and builds are processed through the normal publish path.

Enabled: When Test Mode is enabled, publish operations are routed to the CloudTestr environment, where test cases can be added to the execution queue and queued test cases are executed sequentially according to their configured order.

Key Capabilities

Sequential Test Execution
Add multiple test cases to a queue and execute them in a defined order. This helps maintain a consistent execution sequence for related or dependent test scenarios.

Immediate Mode Switching
Enable or disable Test Mode directly from the panel without modifying the build configuration or restarting the system.

Centralized Status Monitoring
View the current execution mode from a single interface before initiating or modifying test execution.

CloudTestr Validation
Route publish operations to the CloudTestr environment for build and test validation before using the standard publishing workflow.

Best Practices

a. Review running and queued test cases before switching modes.
b. Use Test Mode for build validation before proceeding with standard publishing.
c. Disable Test Mode after testing is complete to restore the standard publishing workflow.

Share this Doc

Test Operation

Or copy link

CONTENTS
Robility Chatbot
Robility Assistant
Online