id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
20721	HorizontalVerticalFilterSeleniumChromeTests.test_basic test failure	Tim Graham	nobody	"Using selenium 2.33.0, Chrome 28.0.1500.71 and chromedriver_linux64_2.1.zip (ChromeDriver server for linux64 (v2.1.210060.dyu) supports Chrome v27-30):
{{{
./runtests.py --settings=test_sqlit admin_widgets.tests.HorizontalVerticalFilterSeleniumChromeTests.test_basic

======================================================================
FAIL: test_basic (admin_widgets.tests.HorizontalVerticalFilterSeleniumChromeTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File ""/home/tim/code/django/tests/admin_widgets/tests.py"", line 664, in test_basic
    self.execute_basic_operations('vertical', 'students')
  File ""/home/tim/code/django/tests/admin_widgets/tests.py"", line 617, in execute_basic_operations
    self.assertActiveButtons(mode, field_name, True, False, True, False)
  File ""/home/tim/code/django/tests/admin_widgets/tests.py"", line 555, in assertActiveButtons
    self.assertEqual(self.has_css_class(choose_link, 'active'), choose)
AssertionError: False != True

}}}

This is testing if selecting options in the horizontal and vertical filter widgets enables the add/remove buttons to move the options from one select to the other. In debugging the test, I see the options are selected, but the button is not enabled (hence the test failure). However, manually clicking the options as opposed to having selenium ""click"" them, does enable the button, so it may be a bug with the Chrome/Selenium interaction.

This is reproducible on master/1.5/1.4 (which is all I tested)."	Bug	closed	Testing framework	1.5	Normal	fixed			Accepted	0	0	0	0	0	0