The Browser library handles downloads by creating a "promise." Because clicking a download button is an asynchronous action (the browser must start the stream while the script continues), you must tell the library to listen for the download event before you trigger it. Basic Download Example robotframework
: Run rfbrowser init to download the required Playwright browser engines (Chromium, Firefox, WebKit). 2. The Core Mechanism: Promise To Wait For Download
${dl_promise}= Promise To Wait For Download Click "Download Report" ${file_info}= Wait For ${dl_promise} # The object contains 'suggestedFilename' and 'saveAs' (the actual path) Log Downloaded file is: ${file_info.suggestedFilename} Use code with caution. 4. Setting a Global Download Directory robot framework browser library download file
Master Guide: Downloading Files with Robot Framework Browser Library
: Specifies the path and filename where the file should be saved. By default, the library saves files with a unique GUID name. The Browser library handles downloads by creating a "promise
One common challenge is that the Browser library often assigns a random UUID to downloaded files if saveAs isn't specified. To use the filename suggested by the server, you can inspect the ${file_info} object returned by the promise. robotframework
Efficiently handling file downloads is a critical component of modern web automation. While older libraries like SeleniumLibrary often required complex browser profile configurations to manage pop-ups, the Robot Framework Browser library —powered by Playwright —provides a much more streamlined and reliable approach. The Core Mechanism: Promise To Wait For Download
: This keyword resolves the promise, ensuring the test doesn't proceed until the download is finished. 3. Handling Dynamic Filenames