[chromedriver] Restore test_expectations.

chrome/test/chromedriver/test/run_java_tests.py

Index: chrome/test/chromedriver/test/run_java_tests.py
diff --git a/chrome/test/chromedriver/test/run_java_tests.py b/chrome/test/chromedriver/test/run_java_tests.py
index 72595332c109abd993492ac274bb1750d27928c0..76ecaf33e1e05852f7fb77ef9812f6d80597be3b 100755
--- a/chrome/test/chromedriver/test/run_java_tests.py
+++ b/chrome/test/chromedriver/test/run_java_tests.py
@@ -18,7 +18,7 @@ import sys
 import xml.dom.minidom as minidom
 
 _THIS_DIR = os.path.abspath(os.path.dirname(__file__))
-sys.path.insert(0, os.path.join(_THIS_DIR, os.pardir))
+sys.path.insert(1, os.path.join(_THIS_DIR, os.pardir))

[frankf, 2013/08/09 23:37:50]

But what are these modules in the top-level instead of being in test/? They're
all used for testing right. You cam make your life much easier to have all the
python test file in the same dir.

[chrisgao (Use stgao instead), 2013/08/10 00:04:20]

Yes, this solution is not perfect.

It's just a workaround because *.pyc is not automatically cleaned up in the bots
and locally if a *.py is removed.

Ideally, if we had dependencies on different modules located in different
directories, we may have to isolate each of them. But I don't think it is a good
idea for the case here, as we have so few and simple modules.

I did ask Ken to move all *.py to chromedriver/test. He insisted some *.py are
to trigger the test but not the test itself.

So TBR for Ken.

 
 import chrome_paths
 import test_environment