✨Minor Release 1.1.0

[Snooz82]

🎉 Release Notes

This release contains minor content updates — some fixes and changes due to Robot Framework release.
Changes made are not directly relevant for the exam participants.

---

✨ New Features

🏷️ Versioned Syllabus

Since this version, the hosting of the syllabus allows to access older versions.
The whole Syllabus is available in Version 1.0.1 and 1.1.0 as web-version and PDF download.

by @Snooz82 in PR #92 (Issue #91 )

---

🚀 Glossary

This new Glossary defines and explains terms that are specific for Robot Framework and used in this syllabus as well as in the Robot Framework User Guide. Linking of glossary terms in the text will follow soon.

by @Snooz82 et al in #72

---

📄 PDF Download of the Syllabus

A downloadable PDF version of the syllabus is now available on the welcome page.

---

📝 Content Changes: Syllabus 1.0.1 → 1.1.0

This document lists all meaningful content changes in Syllabus version 1.0.1 and 1.1.0, excluding grammatical and typo fixes.

---

🔍 Keyword Name Matching Algorithm Updated

The order of how Robot Framework resolves keyword names was corrected following the changes of Robot Framework Release 7.1

by @bennyvw in PR #80 (Issue #77 )

In 3.3.2 User Keyword Names:

- - If then a full match is found, that keyword is used.
- - If no full match is found, the prefixes Given, When, Then, And, and But [...] are removed from the called keyword name to find a match.
- - If still no match is found, Robot Framework tries to match the name with keywords that have embedded arguments.
+ - The prefixes Given, When, Then, And, and But [...] are removed from the called keyword name to find a match.
+ - If no match is found, Robot Framework tries to match the name with keywords that have embedded arguments.
+ - If still no match is found, a full match (including possible Given, When, Then, And and But) is tried.

---

🔁 Example Keyword Changed from Run Process to Set To Dictionary

Section 2.5.1.2 was rewritten to use a different example keyword from the Collections library instead of the Process library due to introduction of typed argument interfaces in Robot Framework standard libraries.

by @bennyvw in PR #80 (Issue #74 )

In 2.5.1.2:

- ### 2.5.1.2 Example Keyword Run Process
+ ### 2.5.1.2 Example Keyword Set To Dictionary

The entire section was reworked with new documentation screenshot, argument descriptions, and new code examples for both *varargs and **kwargs usage patterns.

---

➕ New Code Examples for Variable Number of Positional Arguments and Free Named Arguments (See above)

Two new Robot Framework code examples were added in sections 2.5.2.5 and 2.5.2.7.

by @bennyvw in PR #80 (Issue #74 )

In 2.5.2.5 Variable Number of Positional Arguments:

+ Example adding items to a dictionary using the key_value_pairs argument:

*** Test Cases ***
Dictionary Handling
    VAR   &{mydict}
    Set To Dictionary   ${mydict}   key1    value1   key2    value2

In 2.5.2.7 Free Named Arguments:

- Example redirecting stdout and stderr to a file:
- Run Process ping -n 5 -4 localhost stdout=ping_output.txt stderr=ping_error.txt
+ Example adding items to a dictionary using the items argument:
+ Set To Dictionary ${mydict} key1=value1 key2=value2

---

📄 Execution Artifacts Terminology

The misused summary term for all files created by Robot Framework during execution "output files" are now correctly referenced as "execution artifacts".
Execution Artifacts were also before the named term, it was just not consistently used in the syllabus.

by @Snooz82 in PR #98 (issue #97 )

In 2.3.2 Execution Artifacts:

- Robot Framework, by default, generates three output files in the output directory.
+ Robot Framework, by default, generates three files in the output directory.

In 5.1.4 Built-In Variables:

- ${OUTPUT_DIR} — directory where output files [...] are written
+ ${OUTPUT_DIR} — directory where execution artifacts [...] are written

---

🏷️ "metadata" → "suite metadata" in Settings Descriptions

The term "metadata" was qualified as "suite metadata" for clarity and for upcoming RF changes.

In 2.1.2.1 Introduction to *** Settings *** Section:

- Additional metadata can be defined by multiple Metadata entries
+ Additional suite metadata can be defined by multiple Metadata entries

In 4.3.3 Allowed Sections in Initialization Files:

- Metadata: Add metadata to the suite.
+ Metadata: Add suite metadata.

---

🏷️ Tags: "metadata" → "meta information"

The word "metadata" was replaced in the tags description.

In 4.4 Tags:

- Tags are free-form text labels that can be assigned to tests|tasks to provide metadata
+ Tags are free-form text labels that can be assigned to tests|tasks to provide meta information

---

📐 Code Example Formatting Improvements

Several code examples in 2.6 Writing Test|Task and 5.2 Control Structures were reformatted with line continuations (...) for better readability and shorter line lengths. No content was changed.

---

📝 Import Paths Explanation Reworded

The guidance on relative vs. absolute paths was clarified.

by @bennyvw in PR #76 (Issue #63 )

In 2.4.3 Import Paths:

- Relative paths are portable as long as they are related to the data file that is importing using them, as long as that relative path is part of the project structure.
+ Relative paths are portable as long as they are defined relative to the importing data file and point to locations within the project structure.

---

🥳 New Contributors

• @bennyvw made their first contribution in Minor textual changes #76
• @hassineabd made their first contribution in (Ch. 1.2.3) Fix PyPI casing and (Ch. 3.5.1) OperatingSystem library name #93

---

🛠️ Fixes

We resolved numerous community-reported issues, including typos, grammar corrections, and improvements to unclear or ambiguous explanations.

🙏 Thanks to everyone who contributed feedback and helped make this release better!

Example issues

• Minor textual changes by @bennyvw in Minor textual changes #76
• (Ch. 1.2.3) Fix PyPI casing and (Ch. 3.5.1) OperatingSystem library name by @hassineabd in (Ch. 1.2.3) Fix PyPI casing and (Ch. 3.5.1) OperatingSystem library name #93
• Fix wrong library attribution in the comment for Append To List by @hassineabd in Fix wrong library attribution in the comment for Append To List #96
• Fix typos in example exam by @hassineabd in Fix typos in example exam #95

Full Changelog: 1.0.1...1.1.0

---

This discussion was created from the release ✨Minor Release 1.1.0.