| Behavior-Driven |
A testing methodology that encourages collaboration between developers, QA, and non-technical stakeholders to define test cases. |
| Data-Driven Specification |
A testing approach where test cases are executed with multiple sets of data to validate functionality. |
| Generic Test Automation Architecture (gTAA) |
A framework that provides a structured approach to test automation, promoting reusability and maintainability. |
| Keywords |
Reusable functions or actions defined in the test automation framework. |
| Keyword-Driven |
A testing approach where test cases are defined using keywords that represent actions or operations. |
| Library |
A collection of keywords and functions that can be used in test automation. |
| Libdoc |
A tool used to generate keyword documentation for libraries and resource files. |
| Rebot |
The main executable used to execute suites and post-process execution results to generate reports. |
| Resource Files |
Files that contain shared keywords and variables that can be imported into test suites. |
| Root Suite |
The top-level suite that contains all other suites and test cases. |
| Suite Directory |
A directory that contains multiple suite files, which can include test cases and tasks organized hierarchically. |
| Suite File |
A *.robot file that contains at least one test case or task. |
| Task |
A unit of work that can be executed, similar to a test case but typically focused on automation tasks. |
| Task Suite |
Suite files that have at least one task and do not contain any test cases. |
| Test Automation |
The use of software tools to execute tests automatically, reducing manual effort. |
| Test Cases Section |
This section defines the executable elements of a suite, specifically test cases. |
| Test Suite |
Suite files that have at least one test case and do not contain any tasks. |
| Tasks Section |
This section defines the executable elements of a suite, specifically tasks. |
| Comments Section |
This section is used to add comments to the suite file or resource file. All content in this section is ignored by Robot Framework. |
| Keyword Section |
This section allows you to define locally scoped user keywords that can only be used within the same suite where they are defined. |
| Robot Framework Sections |
Different parts of a Robot Framework suite file that organize the content. |
| Settings Section |
This section is used to configure various aspects of the test/task suite. |
| Variables Section |
This section is used to define suite variables that are used in the suite or its tests/tasks or inside their keywords. |