Interactive Glossary
Use the search boxes to filter by term or perform a fuzzy free-text search across definitions. Click any row or alias to deep-link to a glossary entry.
| Term | Definition & Abbreviation |
|---|---|
__init__.robot | See Initialization File |
**kwargs | See Free Named Argument |
*args | See Variable Number of Positional Arguments |
*varargs | See Variable Number of Positional Arguments |
Acceptance Testing | Validation that a system satisfies agreed business requirements and is ready for deployment or release. |
Active Monitoring | See Synthetic Monitoring |
Adaptation Layer | Layer in the Generic Test Automation Architecture (gTAA) that connects Robot Framework to the System Under Test or other automated systems via keyword libraries. |
Argument | Value supplied to a keyword call as positional, named, or embedded input to configure its behavior. |
Argument Interface | Ordered specification of a keyword’s arguments, including kinds (for example positional-or-named, named-only, variable positional, free named, embedded), names, default values, and optional type hints. |
Atomic Element | Execution element without child steps whose status depends solely on its own execution result. |
Automation Script | Robot Framework suite, test|task, or keyword collection that automates a defined workflow or behavior. |
Behavior-Driven Development | Development approach that describes system behavior in business-readable language, often using Given/When/Then phrasing. BDD |
Behavior-Driven Specification | Declarative Robot Framework style in which tests|tasks describe system behavior from the user's perspective using natural-language-like steps with embedded arguments and optional Given/When/Then/And/But prefixes. |
Built-In Variables | Variables provided by Robot Framework that expose execution-related information such as paths, timestamps, and status without explicit definition. |
Command Line Interface | Interface used to run Robot Framework from the command line (for example with the |
Composite Element | Execution element composed of child elements (for example suites with tests|tasks, tests|tasks with keywords, or user keywords with child steps) whose status is derived from its children. |
Composite Keyword | See User Keyword |
Control Structure | Statement such as |
Data-Driven Specification | Specification style where the same logic or test flow is executed multiple times with varying input or expected output data, often implemented with test|task templates. |
Definition Layer | Layer in the Generic Test Automation Architecture (gTAA) containing test data such as suites, tests, tasks, resource files, keywords, and variables written in Robot Framework syntax. |
Dictionary Variable | Robot Framework variable of dictionary type created with the &{} |
Embedded Argument | Argument kind defined directly in a keyword name using |
End-to-End Test | Test that verifies a complete workflow across all relevant components, subsystems, and interfaces to ensure real-world user flows behave as expected. |
Execution Artifacts | Files generated by a Robot Framework execution (e.g. |
Execution Layer | Layer in the Generic Test Automation Architecture (gTAA) comprising Robot Framework’s parser, execution engine, logging, and reporting components that interpret test data and run keywords. |
Execution Model | Internal representation created after parsing suites, tests, tasks, and keywords that the execution engine uses to perform automation. |
Fail Status | Execution status indicating that an element (e.g. keyword, test|task, or suite) did not meet its expected outcome or raised an error during execution. |
FOR Loop | Control structure used to iterate over items in a list or other iterable and execute a body of keywords for each item. |
Free Named Argument | Catch-all named argument kind in a keyword specification, marked with **, that gathers all named values not explicitly defined elsewhere into a dictionary. |
Generic Test Automation Architecture | Layered reference architecture for test automation that separates definition, execution, and adaptation layers and describes Robot Framework’s role in an automation solution. |
Given / When / Then / And / But | Conventional prefixes in behavior-driven specification style that Robot Framework can ignore when matching keywords if the remaining part of the name matches a keyword. |
Global Variable | Variable with global scope that can be accessed from all suites and keywords in a Robot Framework execution. |
gTAA | See Generic Test Automation Architecture |
Higher-Level Suite | See Suite Directory |
IF Statement | Control structure in Robot Framework used to execute one block of statements when a condition is true and optionally alternative blocks with IFIF/ELSE |
IF/ELSE | See IF Statement |
Initialization File | Suite file located in a directory that configures that directory as a suite and defines suite-level settings, variables, setups, and teardowns for contained suites. |
Inline Comment | Comment at the beginning or end of a line in a Robot Framework file, separated by at least two spaces and starting with # so that it is ignored by the interpreter. |
Inline IF | Compact single-line IF statement ( |
Keyword | Named reusable action or sequence of actions in Robot Framework callable from tests, tasks, or other keywords that may accept arguments and return values. |
Keyword Interface | Documented information about a keyword, including its name, arguments with kinds and types, return values, documentation, and examples, as exposed by HTML documentation or IDEs. |
Keyword Library | Collection of library keywords implemented typically in Python (or other languages) that Robot Framework imports to interact with external systems, perform computations, or provide utility functions. |
Keyword-Driven Specification | Imperative Robot Framework style where tests|tasks are written as sequences of keyword calls with arguments, focusing on executed actions and their order. |
Knowledge Level | Categorization of learning objectives based on Bloom’s Taxonomy: K1 (Remember), K2 (Understand), and K3 (Apply), indicating expected depth of knowledge. K-Level |
Library | See Keyword Library |
List Variable | Robot Framework variable of list type created with the @{} |
Local Variable | Variable whose scope is limited to a single keyword, test, or task execution and is not visible outside that body. |
Log File | Detailed HTML execution log (log.html) generated by Robot Framework that shows keyword-level execution steps, arguments, messages, and statuses. |
log.html | See Log File |
Mandatory Argument | Argument kind in a keyword specification without a default value that must be provided in calls and that precedes optional arguments. |
Named Argument | Argument value provided in a keyword call using an explicit name=value pair. |
Named-Only Argument | Argument kind in a keyword specification that must be provided by name (never positionally), typically defined after a Variable Number of Positional Arguments or explicitly marked, and that can be mandatory or optional. |
Optional Argument | Argument kind in a keyword specification that may be omitted because it has a default value or is a catch-all (e.g. |
Output File | Primary machine-readable execution result file (e.g. |
output.xml | See Output File |
Pass Status | Execution status indicating that an element (e.g. keyword, test|task, or suite) executed successfully and met its expectations. |
Positional Argument | Argument value provided in a keyword call solely by its position in the argument list without naming it explicitly. |
Positional or Named Argument | Argument kind in a keyword specification that can be set either by position or by name (but not both for the same value) and that may be mandatory or optional. |
Report File | High-level HTML summary ( |
report.html | See Report File |
Resource File | File (commonly with extension .resource or .robot) that contains user keywords and variables and is imported by suites to share and reuse these artifacts. |
RETURN | See RETURN Statement |
RETURN Statement | Statement used in user keywords to return one or more values that can be assigned to variables in the calling context. |
Return Type Hint | Documented indication of the type of value a keyword returns, helping users understand how to use the returned data. |
RFCP | See Robot Framework® Certified Professional |
Robot Framework CLI | See Command Line Interface |
Robot Framework Foundation | Non-profit association (Robot Framework ry) that stewards the development, ecosystem, governance, and promotion of Robot Framework and its community. |
Robot Framework® Certified Professional | Foundational certification level for Robot Framework that validates understanding of core concepts, syntax, and basic control structures. |
Robotic Process Automation | Automation of business processes or tasks normally performed by humans, often across multiple systems, without necessarily focusing on testing. |
Root Suite | Top-level suite in a Robot Framework execution determined by the initial directory or file path passed to the |
RPA | See Robotic Process Automation |
Scalar Access Syntax | Standard variable access form ${} |
Scalar Variable | Robot Framework variable accessed with the |
Skip Status | Execution status indicating that an element (e.g. a test|task) was intentionally not executed, for example due to selection options or an explicit skip. |
Standard Library | Library shipped with Robot Framework itself providing generic functionality such as operating system interaction, string manipulation, or process handling. |
Suite | Collection of tests|tasks (optionally with local keywords and variables) defined in a .robot file or directory that is executed as a unit by Robot Framework. |
Suite Directory | Directory treated as a suite because it directly or indirectly contains at least one suite file, grouping lower-level suites into a suite tree. |
Suite File | .robot file that contains at least one test case or task and is therefore treated by Robot Framework as an executable suite. |
Suite Initialization File | See Initialization File |
Suite Metadata | Key–value information defined with the |
Suite Setup | Keyword executed once before any tests|tasks in a suite are run, typically used to prepare common preconditions. |
Suite Teardown | Keyword executed once after all tests|tasks in a suite have run, typically used to clean up shared resources. |
Suite Variable | Variable whose scope covers all tests|tasks and keywords within a specific suite but is not visible outside that suite. |
Synthetic Monitoring | Proactive monitoring that runs automated scripts (often using tools like Robot Framework) at regular intervals against live systems to detect issues before real users are affected. |
Task | Executable entity in Robot Framework similar to a test case but used for non-testing automation such as RPA workflows, defined in a |
Task Setup | See Test Setup |
Task Suite | See Suite |
Task Tag | See Test Tag |
Task Teardown | See Test Teardown |
Task Template | See Test Template |
Task Timeout | See Test Timeout |
Test | See Test Case |
Test Case | Executable specification in Robot Framework that verifies some aspect of system behavior and is defined in a |
Test Data | Collection of suites, tests, tasks, resource files, keywords, and variables that define what Robot Framework executes. |
Test Level | Classification of testing focus (e.g. unit, component, integration, system, system integration, acceptance, or end-to-end) describing scope and granularity of tests. |
Test Setup | Keyword executed before an individual test|task starts to prepare preconditions specific to that test|task. |
Test Suite | See Suite |
Test Tag | Label assigned to tests|tasks via the Tags setting to categorize them and enable filtering, selection, and reporting. |
Test Teardown | Keyword executed after an individual test|task finishes to clean up resources specific to that test|task. |
Test Template | Setting that defines a keyword used as a template for multiple tests|tasks, where each row of data calls the template keyword with different arguments. |
Test Timeout | Maximum allowed execution time for a keyword, test, or task after which Robot Framework marks the element as failed due to timeout. |
User Keyword | Keyword defined in Robot Framework syntax (typically in suites or resource files) composed of calls to other keywords and statements, often describing higher-level or business-oriented actions. |
Variable | Named reference to a value or collection of values in Robot Framework used to store data and pass it between keywords, tests, and tasks. |
Variable File | File (often a Python module or other supported format) that provides variables which can be imported into suites using the Variables setting. |
Variable Number of Positional Arguments | Optional argument kind in a keyword specification, marked with a single *, that collects all remaining positional values; once present, any subsequent parameters must be provided as named arguments. |
Variable Scope | Visibility and lifetime of a variable (e.g. global, suite, test|task, or local) during a Robot Framework execution. |
WHILE Loop | Control structure in Robot Framework that repeatedly executes a block of keywords as long as a given condition evaluates to true. |