You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
AttributeError: 'Selenium2Library' object has no attribute '*FireFox' #169
I have python 2.6 and I just installed selenium2 trying to run my test case and getting following error:
pybot myFirstTest.txt
myFirstTest :: This is your first test
[ WARN ] Keyword 'Capture Page Screenshot' could not be run on failure: No browser is open
Go To Google Page [Documentation] Go to google page and search som... | FAIL |
AttributeError: 'Selenium2Library' object has no attribute '*FireFox'
[ WARN ] Keyword 'Capture Page Screenshot' could not be run on failure: No browser is open
Open Selenium Page [Documentation] TestCase for open Selenium page | FAIL |
No browser is open
[ WARN ] Keyword 'Capture Page Screenshot' could not be run on failure: No browser is open
Go To Google Page [Documentation] Go to google page and search som... | FAIL |
AttributeError: 'NoneType' object has no attribute 'rfind'
[ WARN ] Keyword 'Capture Page Screenshot' could not be run on failure: No browser is open
Open Selenium Page [Documentation] TestCase for open Selenium page | FAIL |
No browser is open
myFirstTest :: This is your first test | FAIL |
2 critical tests, 0 passed, 2 failed
2 tests total, 0 passed, 2 failed
hmmm....neither Selenium2Library or Selenium use rfind
I bet that error is occuring inside Robot Framework due to your test data not being parsed correctly.
Perhaps copying/pasting from a blog post led to format issue?
To see a stacktrace of the failure you can run Robot Framework with these arguments:
--logLevel DEBUG
For support you are better off posting to user group for Robot Framework.
You can attach logs and test data to forum post so that others can try to reproduce or analyze your issue.
Without seeing the test you are running I can only guess where things went wrong.
Activity
ombre42 commentedon Feb 15, 2013
See the browser names in the [keyword documentation](http://rtomac.github.com/robotframework-selenium2library/doc/Selenium2Library.html#Open Browser)
Use ff or firefox for Firefox instead of *FireFox.
And don't forget to turn off auto update as Selenium usually does not work with the very latest Firefox.
sskhan commentedon Feb 15, 2013
I tried and now its giving me following error:
myFirstTest :: This is your first test
[ WARN ] Keyword 'Capture Page Screenshot' could not be run on failure: No browser is open
Go To Google Page [Documentation] Go to google page and search som... | FAIL |
AttributeError: 'NoneType' object has no attribute 'rfind'
[ WARN ] Keyword 'Capture Page Screenshot' could not be run on failure: No browser is open
Open Selenium Page [Documentation] TestCase for open Selenium page | FAIL |
No browser is open
myFirstTest :: This is your first test | FAIL |
2 critical tests, 0 passed, 2 failed
2 tests total, 0 passed, 2 failed
ombre42 commentedon Feb 15, 2013
hmmm....neither Selenium2Library or Selenium use rfind
I bet that error is occuring inside Robot Framework due to your test data not being parsed correctly.
Perhaps copying/pasting from a blog post led to format issue?
To see a stacktrace of the failure you can run Robot Framework with these arguments:
--logLevel DEBUG
For support you are better off posting to user group for Robot Framework.
You can attach logs and test data to forum post so that others can try to reproduce or analyze your issue.
Without seeing the test you are running I can only guess where things went wrong.
sskhan commentedon Feb 15, 2013
I am trying to run the code on following link:
http://www.wallix.org/2011/07/26/how-to-use-robotframework-with-the-selenium-library/
in common.txt I change Browser to ff instead of chrome
sskhan commentedon Feb 15, 2013
Please any one I am really not able top figure whats the prob is. I remove the proxy and check even then not able to make it work
emanlove commentedon Dec 31, 2013
Unable to reproduce. If this is still an issue please try emailing the mailing list.
ombre42 commentedon Dec 31, 2013
This was fixed in 1.4 by 232