*** Settings *** Library SeleniumLibrary Library OperatingSystem *** Variables *** ${DOWNLOAD_PATH} ${CURDIR}${/}downloads ${FILE_NAME} report.pdf *** Test Cases *** Verify User Can Download Report [Setup] Create Directory ${DOWNLOAD_PATH} # Trigger the download action Click Element id=download-button # Wait for the file to exist (with timeout) Wait Until Created ${DOWNLOAD_PATH}${/}${FILE_NAME} timeout=20s # Final verification File Should Exist ${DOWNLOAD_PATH}${/}${FILE_NAME} [Teardown] Empty Directory ${DOWNLOAD_PATH} Use code with caution. Strategy 2: Configuring Chrome/Edge Preferences
💡 Always use a [Teardown] to delete downloaded files. This prevents subsequent test runs from passing falsely because of a file left over from a previous run.
Use Get File or specialized libraries (like ExcelLibrary or PDFLibrary ) to inspect the data inside. Example: Size and Extension Check robotframework robot framework check download file
Ensure the download finished and didn't result in a 0KB file.
Which are you using? (Selenium or Browser/Playwright) Which browser are you targeting? (Chrome, Firefox, etc.) Use Get File or specialized libraries (like ExcelLibrary
If you are using the newer , handling downloads is much more elegant. It provides a specific Promise To Wait For Download keyword that captures the download event directly. robotframework
💡 If your app generates random filenames, use List Directory from the OperatingSystem library to find the most recently created file instead of hardcoding a name. the operating system
Robot Framework is a powerhouse for automated testing, but verifying file downloads can be tricky because it involves the intersection of your web browser, the operating system, and the automation engine. Unlike clicking a button or typing text, a download happens outside the browser's DOM, meaning Selenium or Playwright tools can't "see" the file directly.