robotframework

I cannot get test level variables to appear in documentation. Let's say I have this testsuite: | *Variables* | | ${SystemUnderTest} = | Staging | *testcase* | | Device Test | | | Set Test Variable | ${device} | iPhone | | [Documentation] | Device is: ${device} | | | ... | System is: ${SystemUnderTest} | | | No Operation That produces this log: TEST CASE: Device TestExpand All Full Name: T.Device Test Documentation: Device is: ${device} System is: Staging Notice that the Suite level variable is treated properly, but the test level one is not. How do I get all variables to be treated equally?

I just started working on Robot Framework and I am trying to use Try Keyword If keyword, but all the examples I see online show the solution in a single line whereas I have columns and rows in RIDE. If I have a button with the ID of "Current Status" on the current page then I want to go to URL www.xyz.com and perform some action. The confusion is when I write Run Keyword If in the first cell of a test case in RIDE, what should I write in second column? Should this be the Page Should Contain ? or Page Should Not Contain ? Please let me know what information I am missing for above. Bryan Oakley

Can someone explain me how to use default values for optional keyword arguments in connection with data-driven testcases? As you can see in my example not all default values are used in some cases: *** Test Cases *** | testArgs | [Template] | doSomething | | 111 : 222 : 333 : 444 | | xxx : 222 : 333 : 444 | xxx | | 111 : xxx : 333 : 444 | | xxx | | 111 : xxx : 333 : 444 | ${EMPTY} | xxx | | None : xxx : 333 : 444 | ${None} | xxx | | None : xxx : 333 : 444 | ${null} | xxx | | 111 : 222 : xxx : 444 | | | xxx *** Keywords *** | doSomething | | [Arguments] | ${expected} | ${arg1}=111 | ${arg2}=222

How can I specify blank/empty value for a text field when using the robotframework-seleniumlibrary with a TSV file? For example, I have the following: Textfield Value Should Be identifier=name1 Chris Textfield Value Should Be identifier=name2 I want to test that name2 is blank. I have tried leaving it blank (which returns a message about an incorrect number of arguments. I have tried "", which looks for a pair of quotes, and '' which enters a single quote, and selenium seems to look for that janne You can use either a single backslash \ or special variable ${EMPTY} to create an empty string in

Suppose I have 2 test suites in the local directory, foo and bar, and I want to run the test suite in the order of foo then bar. I tried to run pybot -s foo -s bar . , but then it just goes and run bar then foo (i.e. in alphabetical order). Is there a way to get pybot to run robot framework suites to be execute in the order that I define? Robot framework can use argument files that can be used to specify order of execution ( docs ): This is from older docs (not online anymore): Another important usage for argument files is specifying input files or directories in certain order. This can be

I'm trying to write a test case in robot framework to download an excel file automatically from a web-site. I want to set preferences for my browser using robot scripts to download files automatically in my desired destination directory without asking me! I have tried this solution ; but it didn't work. I also tried to set an existing firefox profile as this says which works fine, but I want to be capable of automatically adjusting preferences. Any idea? As @Sachin said I wrote a python script to set preferences for FireFox as well: from selenium import webdriver class WebElement(object):

I'm experimenting with running my RF/Selenium2Library tests from Jenkins on my OSX laptop. Jenkins is installed as default as user 'jenkins'. I have the RF plugin for Jenkins installed and environment variables set, and everything works fine EXCEPT the browser never opens (neither firefox nor chrome) and the tests fail with selenium timeouts saying that such and such element never appeared. My hunch is that I need to set a display variable somewhere to get the browser to open properly. Here's my 'execute shell' command from Jenkins for this project: source /Users/Shared/Jenkins/.bash_profile;