Generate Robot Framework tests with keyword-driven syntax

Generates Robot Framework tests in keyword-driven syntax with Python, covering SeleniumLibrary, RequestsLibrary, and custom keywords. Core patterns include a basic UI test suite with Suite Setup/Suite Teardown opening and closing the browser, explicit waits before interaction (Wait Until Element Is Visible), and both a happy-path login and an invalid-credentials-shows-error case; custom keywords that wrap repeated steps (a Login As User keyword taking email/password arguments, a Verify Dashboard Is Displayed keyword) so test cases read as short, readable flows; data-driven tests via the [Template] mechanism, where one Login And Verify keyword is run against multiple email/password/expected-result rows without repeating the test body; API testing with RequestsLibrary using GET/POST keywords, expected_status assertions, and JSON body dictionaries built with Create Dictionary; and cloud execution config pointing remote_url at a LambdaTest hub URL built from %{LT_USERNAME}/%{LT_ACCESS_KEY} environment variables with capabilities like browser name/version, platform, and video recording set via LT:Options. Setup is pip install robotframework robotframework-seleniumlibrary robotframework-requests, tests run via robot tests/ (or robot --include smoke tests/ to filter by tag), and report.html/log.html are generated automatically. A deeper reference playbook covers ten production-grade sections: project setup (structure, variable files, pabot parallel execution), web UI testing with Page Objects and dynamic content handling, API testing CRUD with error handling and auth, data-driven testing via DataDriver with CSV and FOR loops, custom Python libraries using the @keyword decorator, the Playwright-based Browser Library for modern testing with network interception, LambdaTest remote/cross-browser integration, CI/CD integration with GitHub Actions matrix strategy and parallel report merging, a 12-item debugging table of common problems and fixes, and a 14-item best-practices checklist.

*** Settings ***
Library    SeleniumLibrary
Suite Setup    Open Browser    ${BASE_URL}    chrome
Suite Teardown    Close All Browsers

*** Variables ***
${BASE_URL}    http://localhost:3000
${EMAIL}       user@test.com
${PASSWORD}    password123

*** Test Cases ***
Login With Valid Credentials
    Go To    ${BASE_URL}/login
    Wait Until Element Is Visible    id:email    10s
    Input Text    id:email    ${EMAIL}
    Input Text    id:password    ${PASSWORD}
    Click Button    css:button[type='submit']
    Wait Until Element Is Visible    css:.dashboard    10s
    Page Should Contain    Welcome
    Location Should Contain    /dashboard

Use it whenever a user mentions Robot Framework, *** Test Cases *** syntax, SeleniumLibrary, or a .robot file, or wants keyword-driven UI or API tests written in Robot Framework's syntax.

Input is a UI flow or API endpoint to test, or a set of data rows to test against. Output is a .robot test file with settings/variables/test cases (and custom keywords when reuse is needed), runnable via the robot CLI with auto-generated HTML report and log files.

Uses SeleniumLibrary for browser UI testing, RequestsLibrary for API testing, the DataDriver library for CSV-driven tests, the Playwright-based Browser Library as a modern alternative, pabot for parallel execution, and LambdaTest's remote hub for cross-browser cloud execution.

QA engineers and developers writing Robot Framework tests who want correct keyword-driven syntax for UI, API, and data-driven test cases, plus a deeper playbook for production patterns like Page Objects, custom Python keywords, and CI/CD integration.