Allow webdriver users to choose between sending the key events when...

chrome/test/webdriver/chromedriver_tests.py

Index: chrome/test/webdriver/chromedriver_tests.py
===================================================================
--- chrome/test/webdriver/chromedriver_tests.py	(revision 76851)
+++ chrome/test/webdriver/chromedriver_tests.py	(working copy)
@@ -108,6 +108,7 @@
     except urllib2.HTTPError, expected:
       self.assertEquals(404, expected.code)
 
+class BasicServerTest(unittest.TestCase):
   def testCanStartChromeDriverOnSpecificPort(self):
     launcher = ChromeDriverLauncher(port=9520)
     self.assertEquals(9520, launcher.GetPort())
@@ -115,7 +116,14 @@
     driver.quit()
     launcher.Kill()
 
+  def testCanStartChromeWithNativeEventsEnabled(self):
+    launcher = ChromeDriverLauncher(use_native_events=True)
+    self.assertTrue(launcher.GetUseNativeEvents())
+    driver = WebDriver(launcher.GetURL(), 'chrome', 'any')

[Jason Leyba, 2011/03/04 19:25:12]

You're not verifying that the server has actually started with native events
enabled.

[timothe faudot, 2011/03/07 02:45:26]

This test only ensures that we can start the server with the flag
--native-events set and that it is stored in the session manager. For the test
that send key events it is in
webdriver_remote_tests.py/RemoteWebdriverNativeEventsTest

[Jason Leyba, 2011/03/07 03:32:56]

That's my point - you're only testing that you can start the server with the
--native-events flag and create a session.  There's nothing about this test that
verifies the server did anything with the --native-events flag.
I don't see any changes to webdriver_remote_tests in the latest patch.

+    driver.quit()
+    launcher.Kill()
 
+
 class CookieTest(unittest.TestCase):
   """Cookie test for the json webdriver protocol"""