In recent times i have tried downloading pdf files from chrome and got stuck with setting chrome options in robot framework.
Did searched through all possible ways and found the solutions. which took lot of time to understand the syntax in robot.
Please add recipes for different types of driver setup in robot framework with all desired capabilities. it will be lot useful for beginners. Attaching code snippet am using now for reference.

*** Variables ***
${BROWSER}                  chrome
${DOWNLOAD_DIR}             ${CURDIR}/../temp
${REMOTE URL}               http://127.0.0.1:4444/wd/hub
&{OPTION}
&{DESIRED_CAPABILITIES}     name=browserTest    enableVNC=${True}

*** Keywords ***
Login To OMS
    [Documentation]    login for oms
    ${profile}    Create dictionary    enabled=${False}    name=Chrome PDF Viewer
    ${list profile}    Create list    ${profile}
    ${prefs}    Create Dictionary    plugins.plugins_list=${list profile}
    ...    plugins.always_open_pdf_externally=${True}
    ...    download.extensions_to_open=applications/pdf    download.prompt_for_download=${False}
    ...    safebrowsing.enabled=${True}    download.default_directory=/../temp
    ${chrome options}    Evaluate    sys.modules['selenium.webdriver'].ChromeOptions()    sys, selenium.webdriver
    Call Method    ${chrome options}    add_experimental_option    prefs    ${prefs}
    Open Browser    ${LOGIN URL}    ${BROWSER}    desired_capabilities=${DESIRED_CAPABILITIES}
    ...    options=${chrome options}

Currently, Cookbook dives straight in with recipes showing how to use keywords from certain libraries but there is no explanation of the basic structure and tables that together form a test suite. Beginners especially might not have enough context to understand even the most basic recipe.

There was also a request on Slack to show what you can do with Metadata in the *** Settings *** section.

We should be careful not to repeat the information contained in the User Guide which covers this in some detail.

Please note, this should not be added to beginning of the Table of Contents section as it will renumber all the proceeding sections and require significant refactoring. Perhaps a new section Introduction before Table of Contents.

It would be useful to have a recipe that demonstrates basic usage of the external SSH Library.

Beginners get confused that commands are always executed in a new shell so it would be good to also demonstrate how to execute commands in an interactive session.

Process library can be used for tests that run processes.

This recipe could demonstrate how to use the following keywords:

• Start Process
• Run Process
• Wait For Process
• Terminate Process
• Terminate All Processes

Also check the example in the documentation although a working script is preferred for all recipes in Cookbook.

A common use case is to import a list of values or test data from an external data file, e.g. CSV or Excel.

A recipe demonstrating how to do this would be useful for many test case scenarios.

The cookbook recipes are all using 'Force Tags' which is now deprecated since RF Version 6.0. Update recipes to use 'Test Tags'.

Robocopy is scanning our recipes each time a change is made in this repo and it had detected this deprecated keyword.

Log message:
/home/runner/work/robotframework-cookbook/robotframework-cookbook/src/section_03/recipe031_handling_dates.robot:12:1 [W] 0319 'Force Tags' is deprecated since Robot Framework version 6.0, use 'Test Tags' instead (deprecated-statement)

String library can be used for string manipulation and verification.

This recipe could demonstrate how to use the following keywords:

• Convert To Lower Case
• Should Be Lowercase
• Convert To Title Case
• Should Be Titlecase
• Convert To Upper Case
• Should Be Uppercase
• Replace String

Robot Framework 5 brings several new syntax features:

• Native TRY/EXCEPT
• WHILE loop
• RETURN statement
• Inline IF
• BREAK & CONTINUE

Create recipes to demonstrate how to use the new syntax.

For more information see:
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

I have assumed since the beginning of this project that those interested in Robot Framework - Cookbook know how to clone a github repo, install the required Python libs and run the recipes, but that may not be the case for everybody.

Add Installation and Usage section(s) to README explaining how to set up this repo locally, install packages and execute the Robot Framework recipes.

Also explain that libs can be installed using the relevant requirements*.txt document located in the tests folder.

Database views should be regularly tested to ensure that they are still functioning. Views are effectively a SELECT statement that queries data from database tables and other views. The underlying tables and join conditions that the view depends on can be modified in a way that breaks existing views if they have not been refactored in line with new db structure.

First, it is necessary to query the database catalog and loop through all database views that exist. For each view discovered, a simple "SELECT TOP 1 * FROM <database_view>;" will be sufficient to check that the view logic is still functioning. This technique should work even if there is no data loaded.

This would be a nice feature and encourage contributions. I saw it recently on the rf-browser project: https://github.com/MarketSquare/robotframework-browser

Add automated Contributors section to main README using this project: https://github.com/all-contributors/all-contributors

Robot Framework Cookbook may be the first stop for beginners or those new to Robot Framework.

The README should be updated to include links to other primary information sources for beginners so they may explore further.

Examples:

• Robot Framework Organization
• Robot Framework User Guide
• Robot Framework Documentation
• GitHub

All Python code in the project should be formatted using Black code formatter:
https://black.readthedocs.io/en/stable/index.html

Use Black default options, i.e. no overriding recommendations for vertical hanging indents, double-quotes everywhere and maximum line length (88). Also dispay a badge at the top of the main README showing that this project enforces Black code formatting for Python code. Exceptions may be required for Case Study material.

GitHub Actions documentation can be found here:
https://black.readthedocs.io/en/stable/github_actions.html

Good feedback on the Slack channel (#cookbook) from Rene.

Recipe 21 mentions that beginners often struggle with the variable prefixes $ and @ and how/what they actually do but recipe 21 itself does not attempt to explain their use. Instead, the recipe just shows the different prefixes being used in a sample script without explanation.

Add explanation of $ and @ prefixes and how they affect the variable usage.

Create a simple logo for Cookbook. The idea I had in mind is a black and white logo similar to the Robot Framework logo with a chef's hat (toque) of course 😉

It would be helpful to have at least a basic recipe to demonstrate the features of Robot Framework Browser.

See here for more details:
https://github.com/MarketSquare/robotframework-browser

I would like to add CI to this repo, something like Travis-CI or GitHub Actions are both great.

Can you help show me the way?

The CI workflows for this project currently support Python versions 3.7, 3.8 and 3.9.
Remove support for Python 3.7 and add support for Python 3.10.

Actions:

• Remove py3.6 from all tests in cookbook project and add py3.9
• Browser tests are failing, fix or remove from CI
• PABOT tests are failing but this could be linked to the py tags issue

Testing the new CI process has revealed a few errors with missing mandatory variables in recipe 141:

robotframework-cookbook\src\section_14\recipe141_aws_simple_storage_service.robot:18:0 [E] 5504 Missing mandatory '${level}' variable in *** Variables *** section
robotframework-cookbook\src\section_14\recipe141_aws_simple_storage_service.robot:18:0 [E] 5504 Missing mandatory '${category}' variable in *** Variables *** section
robotframework-cookbook\src\section_14\recipe141_aws_simple_storage_service.robot:18:0 [E] 5504 Missing mandatory '${recipe}' variable in *** Variables *** section

Solution:
Add the following variables to Variables table/section in line with all other recipes in cookbook:

${level}
${category}
${recipe}

Display a chart of Star History for this repo in README document

It would be helpful to explain the contributing process and guide contributors so they can effectively submit their work.

Consider:

• Development and testing standards that should be followed
• Working on a fork repo
• Cloning repo
• Branch naming
• Pull request usage
• Recognition in Contributors section

We don't currently have any recipes with *** Keywords *** section/table that demonstrate how to create your own user keywords.

For example, in section 9 we could rewrite Recipe 091 Working With Requests Library so we have new keyword Check Github User Exists and Check Github User Does Not Exist

The test case Get Request test case could be rewritten to check several accounts that do exist and several accounts that should not exist.

It was necessary to disable CI testing for Recipe 15.1 as there were problems setting geolocation permission. This test has previously worked but something has changed during the last year and CI testing is now failing.

Demonstrate how faker library allows easy use of Faker's random test data generation in Robot Framework.

More information:
https://github.com/guykisel/robotframework-faker

Cookbook is growing. It would be a good time to review the existing recipes and confirm they are all working. We do have CI running using github actions but external libs change as we saw with robocop earlier this year and this can introduce breaking changes.

Most important enhancements:

• New SKIP status
• Criticality has been removed
• Native IF/ELSE syntax
• Support for nested control structures

Reported by Emna Ayadi (@emna24)

Github Actions logs are warning that we are requesting node version 12 which is already deprecated. However, when inspecting the main.yml workflow, I can see references to node-version: [16.x]

Please add a recipe for interacting with a database. SQLite would be a good choice as it is available in all Python and Robot Framework installations.

For example, it would be useful to inspect the database catalog and confirm certain objects like tables and views exist.

It would also be useful to check the data types of columns to ensure we are using the correct schema in a particular database environment.

Include a recipe in the cookbook for setting up seleniumlibrary with the seleniumtestability plugin.