Skip to content

'Select Radio Button' fails to change value in IE and doesn't report failure #101

Closed

Description

@know1nos

pretty self explanatory, but the command works fine in firefox and chrome

Activity

  1. Softworks-Consultancy commented on Aug 30, 2012

    @Softworks-Consultancy

    does it work with "regular" selenium i.e. without robot framework?

    Also what version of IE?

  2. know1nos commented on Aug 30, 2012

    @know1nos
    Author

    I have not tried it without robotframework, relatively new to selenium and robotframework alike. I am currently using IE9.

  3. emanlove commented on Aug 31, 2012

    @emanlove
    Member

    @know1nos: I recently had an issue for which I needed to test selenium without robotframework. Here are the steps I took (sorry but they are written for Linux. at least the unittest script is not OS dependent) ...

    Setup a python virtual environment to isolate my test environment

    ~$ mkdir se-bug 
    ~$ cd se-bug
    ~/se-bug$ virtualenv -p /usr/bin/python2.6 --no-site-packages clean-python26-env
    

    Activate the virtual enviroment and install selenium; in this case I specify selenium version 2.25.0 (the version I was having problem with)

    ~/se-bug$ source clean-python26-env/bin/activate
    (clean-python26-env) ~/se-bug$ easy_install selenium==2.25.0
    

    create a test file ~/se-bug/testExeJS.py

    import unittest
    from selenium import webdriver
    
    class ExecuteJavascriptTestCase(unittest.TestCase):
    
        def setUp(self):
            self.driver = webdriver.Firefox()
    
        def test_exe_javascript(self):
            driver = self.driver
            driver.get("http://www.google.com")
            driver.execute_script("return [ document.location ];")
            print('Finished')
    
        def tearDown(self):
            self.driver.close()
    
    if __name__ == "__main__":
        unittest.main()
    

    and run unittest

    (clean-python26-env) ~/se-bug$ python testExeJS.py
    

    In my case I was having issue with Firefox and the 'execute_script' selenium command. You should be able to create a similar test for the issue you are having.

    Also if you provide more of the error output or traceback we might be able to help more.

  4. know1nos commented on Sep 4, 2012

    @know1nos
    Author

    Thank you, I will go about trying that soon.

    As for the error output there is NONE, half the time the command simply does not change the value but reports that there was no error... I don't know if that helps narrow the problem down but I appreciate any and all responses.

  5. emanlove commented on Sep 4, 2012

    @emanlove
    Member

    There has been some submitted patches (#92) to address the issues of return values and error reporting with the select keywords. I don't think this patch addresses your specific issue but it's a start. I've added a task (#104) for me to review the return value for all keywords within the library.

    Note also I have some changes to the select keywords and @schminitz has some performance patches which should improve the functionality and speed of the select keywords.

  6. emanlove commented on Dec 27, 2013

    @emanlove
    Member

    I've retried this under IE9, Selenium 2.37.2 and it works for me. If this is still an issue please reopen this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions