Hot answers tagged


There are a few ways to do handle this... For Flash Videos: Most flash videos show up in iFrames, so you'll want switch to the iFrame container (using selectFrame) and then do an element test to verify the video content shows up correctly (using waitForElementPresent or verifyElementPresent). As others have mentioned, if you're going to need to interact ...


If you need to validate that the video is there then it is a simple element check. BUT if you need to validate if the video is LOADED than that's a completly other thing. Is the video a flash object? Then use flash selenium. If it is a flex object use ...


Here are some useful posts from Stack Overflow: please compare QTP, RIATest , Selenium for Flex Application Automation Testing Automated testing of FLEX based applications Flex UI testing automation Flex automated acceptance testing tools Adobe Developer Connection also contains some tutorials on Flex testing tools. See for example this page: Test and ...


It seems like you don't want to report error if element was not found. In such case, the most straight-forward way is to run the keyword and ignore errors if element is not found: Run Keyword And Ignore Error Click Element id=element_id Also, hard-coding sleep intervals can make your tests slow and flaky. Using Wait Until Page Contains is better.


Based on the example of RF keywords list, you should write the condition, in your case should be ${CreateButtonVisible} == 'PASS' Run Keyword If ${CreateButtonVisible} == 'PASS' Create Button


Though I am late but I have some practicals using sfapi.

Only top voted, non community-wiki answers of a minimum length are eligible