Glossary
Overview
This glossary defines key terms and concepts used throughout Test Orchestration documentation and platform.
📖 Technical Terminology
Look up terms to understand:
Platform-specific concepts
Technical terminology
Workflow-related words
Configuration parameters
Best practice terminology
A
Action
A single step within a workflow that performs a specific operation. Actions are the building blocks of workflows and include operations like:
Wait (pause execution)
Retry (repeat failed operations)
Send Email (notification)
Data Hub (data storage/retrieval)
Comments (documentation)
Related: Workflow, Node
API
Application Programming Interface. A set of protocols and tools for building software applications. In Test Orchestration, APIs are used for:
Platform integration
Remote workflow execution
Data exchange
Third-party system communication
Example: POST /api/workflows/execute
Artifact
Output or file generated during workflow execution. Examples include:
Test reports
Execution logs
Screenshots
Data exports
Generated files
Related: Report, Result
B
Backoff Strategy
Algorithm for determining wait times between retry attempts. Common strategies include:
Linear: Each retry waits progressively longer (1s, 2s, 3s)
Exponential: Wait time increases exponentially (1s, 2s, 4s, 8s)
Fixed: Same wait time for all retries (2s, 2s, 2s)
Jittered: Random variation added to avoid thundering herd
Related: Retry, Wait, Error Handling
Best Practices
Recommended approaches for using the platform effectively. Examples include:
Using meaningful workflow names
Adding documentation through comments
Implementing proper error handling
Regular testing and validation
Version control integration
Related: Workflow Patterns, Standards
Block (Deprecated)
Blocks are no longer a supported feature in Test Orchestration. All workflow logic is now implemented through Nodes and Steps connected in sequence. See Nodes for current best practices.
Business Logic
Rules and processes that define how your application works. In testing context, the functionality you're validating through workflows.
Example: "User can only purchase if they have payment method on file"
C
Checkpoint
Verification point in a workflow where you confirm expected state or data. Used for:
Validating execution progress
Breaking down complex workflows
Debugging failed executions
Performance measurement
Related: Assertion, Verification
CI/CD Integration
Connection between Test Orchestration and Continuous Integration/Continuous Deployment pipelines. Allows:
Automated workflow execution on code changes
Test result reporting to CI/CD systems
Gating deployments on test results
Integration with GitHub, GitLab, Jenkins, etc.
Related: Automation, Pipeline
Conditional Execution
Running specific workflow parts based on conditions. Enables:
If/then logic
Decision branching
Dynamic workflow paths
Error-based actions
Example: "If payment fails, execute retry workflow"
Related: Branching, Logic Flow
Configuration
Settings that control how workflows execute. Includes:
Environment variables
Execution parameters
Resource allocation
Timeout settings
Logging levels
Related: Setting, Parameter, Environment
D
Data Hub
Feature for storing and retrieving data during workflow execution. Provides:
Persistent data storage
Session-based storage
Data retrieval across steps
Data versioning
Related: Session Persistence, Data Propagation
Data Propagation
Passing data between workflow steps automatically. Enables:
Output from Step A → Input to Step B
Data transformation
Variable management
State preservation
Related: Variable, Parameter, Data Flow
Debug Mode
Running workflow with enhanced logging and error reporting for troubleshooting. Provides:
Detailed execution logs
Variable inspection
Step-by-step execution
Breakpoints and watches
Related: Logging, Troubleshooting
Dependent Workflow
Workflow that relies on output or execution of another workflow. Creates dependencies:
Sequential workflow chains
Prerequisite validations
Data dependencies
Execution ordering
Related: Workflow Chain, Execution Flow
E
Endpoint
URL or service address that a workflow interacts with. Examples:
API endpoints:
https://api.example.com/usersDatabase endpoints:
db.company.com:5432Email service endpoints
Cloud service endpoints
Related: API, Service, Integration
Environment
Execution context with specific settings and configurations. Common environments:
Development: For testing changes
Staging: Pre-production environment
Production: Live customer environment
QA: Quality assurance environment
Related: Configuration, Deployment, Pipeline
Environment Variable
Named value that can be set and used throughout workflow execution. Used for:
Configuration management
Sensitive data (passwords, tokens)
Test data parameters
Dynamic values
Example: API_KEY, BASE_URL, TEST_USER
Related: Variable, Configuration, Parameter
Error Handler
Logic that executes when a workflow step fails. Can:
Retry the operation
Continue with alternative path
Log error details
Notify team members
Stop workflow execution
Related: Exception, Failure, Recovery
Execution
Single run instance of a workflow with specific inputs and environment. Each execution:
Has unique execution ID
Records start/end time
Captures all logs
Stores results
Can be replayed
Related: Run, Instance, Workflow Execution
Execution Flow
The sequence and order in which workflow steps execute. Can be:
Linear (step 1 → 2 → 3)
Conditional (based on decisions)
Looping (repeated execution)
Related: Workflow, Sequence
Exit Code
Numeric value returned by workflow indicating result:
0: Success1: General failure2: Misuse of shell commandCustom codes: Application-specific
Related: Status, Result
F
Fail-Fast
Strategy to stop workflow on first failure rather than continuing. Enables:
Quick error detection
Reduced execution time
Early feedback
Efficient resource use
Related: Error Handling, Timeout
Filter
Mechanism for selecting specific items based on criteria. Used for:
Filtering test results
Selecting workflow steps
Data filtering
Result refinement
Related: Search, Query
Folder
Organizational structure for grouping related workflows. Provides:
Hierarchical organization
Access control
Logical grouping
Navigation structure
Related: Project, Workspace, Organization
Function
Reusable sequence of workflow steps that can be called multiple times. Enables:
Code reuse
Complexity reduction
Maintenance efficiency
Parameter passing
Related: Action
G
Glossary
Reference document defining technical terms and concepts (this document).
H
Health Check
Lightweight workflow validating system is operational. Typically includes:
Service connectivity check
Database availability check
API responsiveness check
Basic functionality verification
Related: Smoke Test, Validation
I
Integration
Connection between Test Orchestration and external systems. Types:
API integration
Database integration
CI/CD integration
Message queue integration
File system integration
Related: Endpoint, Service, API
Integration Test
Test validating multiple components work together correctly. Focuses on:
Component interactions
Data flow between services
API communication
Service dependencies
Related: Test Type, Unit Test, E2E Test
J
Job
Scheduled execution of workflow at specific time(s). Created through:
Scheduler feature
Cron expressions
One-time scheduling
Recurring scheduling
Related: Schedule, Automation, Trigger
JSON
JavaScript Object Notation. Data format used for:
API requests/responses
Configuration files
Data storage
Parameter passing
Example:
K
Keyword
Reserved word with special meaning in platform. Examples:
if,then,else(conditional logic)loop,foreach(iteration)try,catch(error handling)wait(delay)
Related: Syntax, Command
L
Logging
Recording of workflow execution details and events. Types:
Debug logs: Detailed information
Info logs: General information
Warning logs: Potential issues
Error logs: Failures and exceptions
Related: Debugging, Troubleshooting
Loop
Workflow step that repeats execution of steps. Can loop:
Fixed number of times
Until condition is met
For each item in collection
With timeout limit
Example:
Related: Iteration
M
Mock
Simulated object or service replacing real implementation for testing. Used for:
Testing without dependencies
Simulating error conditions
Performance testing
Isolated unit testing
Related: Stub, Test Double
Module
Reusable, self-contained unit of functionality. Examples:
Test module
Data module
Notification module
Authentication module
Related: Component, Plugin
N
Node
Individual element within workflow structure. Can be:
Action node (performs operation)
Decision node (conditional logic)
Loop node (iteration)
Test node (executes test script)
Related: Action, Workflow
Notification
Alert or message sent during/after workflow execution. Can notify via:
Email
Slack/Teams
Webhook
SMS
In-app notification
Related: Alert, Action Type
O
Output
Result or data produced by workflow step. Can be:
Text/log output
Data object
File artifact
Status code
Variable assignment
Related: Result, Artifact, Return Value
P
Parameter
Variable passed to workflow or action controlling behavior. Examples:
timeout: 30(execution timeout)retry_count: 3(number of retries)email: [email protected](input data)
Related: Variable, Argument, Setting
Pipeline
Sequence of stages/workflows executing in order. Common in:
CI/CD systems
Data processing
Test automation
Release workflows
Related: Workflow Chain, Automation
Plugin
Extension adding functionality to platform. Enables:
Custom actions
New integrations
Extended capabilities
Related: Extension, Module, Integration
Polling
Repeatedly checking for condition/state change. Used for:
Waiting for async operations
Status checking
Data availability
Event detection
Related: Wait, Retry, Synchronization
Project
Top-level container organizing workflows and settings. Contains:
Workflows
Configurations
Credentials
Scheduled jobs
Team members
Related: Folder, Workspace, Organization
Q
Query
Request for specific data or information. Used for:
Finding workflows
Filtering results
Searching logs
Data retrieval
Related: Filter, Search, API
Queue
Ordered list of items waiting for processing. Used for:
Workflow execution queue
Task scheduling
Message queuing
Job scheduling
Related: Schedule, Job, Pipeline
R
Regression
Unintended behavior change caused by recent code changes. Testing ensures:
Previous fixes remain fixed
New features don't break existing functionality
Quality maintained after updates
Related: Test, Quality Assurance
Report
Document summarizing workflow execution results. Includes:
Execution summary
Step-by-step results
Error logs
Performance metrics
Artifacts
Related: Result, Artifact, Summary
Result
Outcome of workflow execution. Can be:
Passed: All validations succeeded
Failed: One or more validations failed
Skipped: Intentionally not executed
Timeout: Exceeded time limit
Related: Status, Output, Execution
Retry
Re-execution of failed step with same or different parameters. Configured with:
Number of retry attempts
Backoff strategy
Timeout between retries
Failure conditions
Related: Error Handling, Backoff, Resilience
Rollback
Reverting workflow to previous state on failure. Enables:
Recovery from failures
Undoing changes
Cleanup operations
State restoration
Related: Recovery, Error Handling
S
Schedule
Trigger for automatic workflow execution at specific times. Types:
Cron-based (e.g., "every Monday at 9am")
Interval-based (e.g., "every 4 hours")
Event-based (e.g., "on deployment")
Manual trigger
Related: Job, Automation, Trigger
Scheduler
Feature for scheduling automatic workflow execution. Provides:
Recurring execution
One-time scheduling
Time zone support
Execution history
Notification on failure
Related: Schedule, Job, Automation
Scope
Visibility and accessibility level of variable or setting. Scopes include:
Global: Accessible everywhere
Project: Accessible within project
Workflow: Accessible within workflow
Step: Accessible within step
Related: Variable, Visibility, Context
Session
Execution context maintaining state across multiple workflow steps. Enables:
Data persistence
Variable storage
State management
Cross-step communication
Related: State, Context, Session Persistence
Session Persistence
Feature maintaining workflow data/state across steps and executions. Enables:
Long-running workflows
Multi-step processes
State recovery
Data continuity
Related: Session, Data Hub, State
Smoke Test
Quick validation test checking if system works at basic level. Typically:
Runs in <15 minutes
Covers critical paths
Detects obvious issues
Used as gating test
Related: Test Type, Health Check
Snapshot
Point-in-time capture of workflow state/data. Used for:
Debugging
State recovery
Performance analysis
Rollback
Related: Checkpoint, Backup, State
Status
Current state of workflow execution. Possible values:
Running/Executing
Passed/Failed
Skipped
Timeout
Cancelled
Related: Result, State
Step
Individual executable unit within workflow. Can be:
Action step
Decision step
Loop step
Block step
Notification step
Related: Action, Node, Workflow
T
Tag
Label or identifier applied to workflows, projects, or results for:
Organization
Filtering
Categorization
Quick identification
Example: critical, regression, smoke, e2e
Template
Pre-built workflow pattern reusable across projects. Includes:
Common workflow structure
Standard actions
Best practices
Configuration options
Related: Workflow Template, Pattern
Test Case
Defined test scenario with inputs, steps, and expected results. Components:
Name/ID
Preconditions
Test steps
Expected results
Actual results
Related: Test, Workflow, Scenario
Test Data
Sample data used in test workflows. Types:
Positive test data (valid inputs)
Negative test data (invalid inputs)
Edge case data (boundary values)
Production-like data
Related: Input, Parameter, Fixture
Test Suite
Collection of related test cases executed together. Organized by:
Feature
Module
Risk level
Execution frequency
Related: Test Case, Batch, Collection
Timeout
Maximum duration for workflow step or entire execution. Protects against:
Hanging processes
Infinite loops
Unresponsive services
Resource waste
Example: timeout: 3600 (1 hour)
Related: Duration, Limit, Fail-Fast
Trigger
Event or condition causing workflow execution. Types:
Manual trigger (user initiated)
Schedule trigger (time-based)
Webhook trigger (event-based)
Dependency trigger (another workflow completes)
Related: Event, Automation, Scheduler
Troubleshoot
Process of diagnosing and fixing workflow issues. Includes:
Analyzing logs
Checking configurations
Testing components
Applying fixes
Related: Debug, Diagnostic, Issue
U
Unit Test
Test of individual component in isolation. Focuses on:
Single function/method
Controlled inputs
Mocked dependencies
Specific behavior
Related: Test Type, Integration Test, E2E Test
V
Validation
Checking that data or behavior matches expected values. Types:
Data validation (format, range, content)
Behavior validation (expected actions)
State validation (correct state reached)
Response validation (correct response received)
Related: Assertion, Checkpoint, Verification
Variable
Named container for storing values used in workflow. Types:
String: Text values
Number: Numeric values
Boolean: True/False
Array: Collection of values
Object: Complex data structures
Related: Parameter, Constant, Environment Variable
Verification
Confirmation that expected state/behavior achieved. Part of:
Test execution
Checkpoint validation
Result checking
Assertion
Related: Validation, Assertion, Checkpoint
W
Wait Action
Action that pauses workflow execution for specified duration. Used for:
Simulating real-world delays
Allowing async operations to complete
Synchronization
Rate limiting
Related: Pause, Delay, Timeout
Webhook
URL endpoint receiving event notifications from external systems. Enables:
Event-driven workflows
Third-party integrations
Real-time triggers
Bidirectional communication
Related: Integration, Trigger, Notification
Workflow
Sequence of steps/actions automated together. Components:
Steps/Actions
Decisions/Conditionals
Loops/Iterations
Error handling
Notifications
Related: Automation, Process, Script
Workflow Execution
Single run instance of workflow. Includes:
Execution ID
Start/end time
Steps executed
Results produced
Logs captured
Related: Execution, Instance, Run
Workflow Pattern
Reusable workflow structure solving common problems. Examples:
Sequential pattern
Fork-join pattern
Retry pattern
Fallback pattern
Related: Template, Best Practice, Pattern
X
XML
Extensible Markup Language. Data format used for:
API responses (legacy)
Configuration files
Data import/export
SOAP communications
Example:
Y
YAML
Human-readable data serialization format used for:
Configuration files
Workflow definitions
CI/CD pipelines
Template storage
Example:
Z
Zone
Geographic region or logical grouping for:
Data residency
Deployment targets
Execution location
Access control
Acronyms
API
Application Programming Interface
Interface for software communication
CI/CD
Continuous Integration/Deployment
Automated code pipeline
CSV
Comma-Separated Values
Data format
E2E
End-to-End
Complete user journey testing
ETL
Extract-Transform-Load
Data processing pattern
JSON
JavaScript Object Notation
Data format
QA
Quality Assurance
Testing and validation
REST
Representational State Transfer
API architecture style
SOAP
Simple Object Access Protocol
XML-based API protocol
SQL
Structured Query Language
Database query language
URL
Uniform Resource Locator
Web address
YAML
YAML Ain't Markup Language
Data format
XML
Extensible Markup Language
Data format
Related Topics
CLI Reference - CLI terminology and commands
FAQs - Common questions about terms
Troubleshooting - Diagnostic terminology
Core Concepts - Conceptual definitions
Summary
Glossary provides terminology definitions
Terms organized alphabetically
Examples for many concepts
Cross-references for related topics
Acronyms table for common abbreviations
Next: Check FAQs for common questions.
Last updated