2010-04-19 Dirk Pranke <dpranke@chromium.org>
authordpranke@chromium.org <dpranke@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 20 Apr 2010 00:53:22 +0000 (00:53 +0000)
committerdpranke@chromium.org <dpranke@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 20 Apr 2010 00:53:22 +0000 (00:53 +0000)
commit2a2cf9f32369e892758609ccb1ad310019db8878
treee48ed7b4ca5515bd3985121b17501344b1b95254
parent698ab343ea30a2cd1b78b9204c4f510509f1eeef
2010-04-19  Dirk Pranke  <dpranke@chromium.org>

         Reviewed by Adam Barth.

         new-run-webkit-tests - repurpose the "Passing" port as "Dryrun" port
         that can be used to test platforms other than the one you are running
         on. This can be useful for checking baselines and testing code
         coverage.

         Note that running the code on the "wrong" port requires each
         port-specific implementation to actually not require any
         platform-specific python code (e.g., the chromium-win port must
         test for the existence of windows functions before calling them).

         https://bugs.webkit.org/show_bug.cgi?id=37782

         * Scripts/webkitpy/layout_tests/port/chromium_win.py:
         * Scripts/webkitpy/layout_tests/port/dryrun.py: Renamed from WebKitTools/Scripts/webkitpy/layout_tests/port/passing.py.
         * Scripts/webkitpy/layout_tests/port/factory.py:
         * Scripts/webkitpy/layout_tests/run_webkit_tests_unittest.py:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@57860 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKitTools/ChangeLog
WebKitTools/Scripts/webkitpy/layout_tests/port/base.py
WebKitTools/Scripts/webkitpy/layout_tests/port/chromium_win.py
WebKitTools/Scripts/webkitpy/layout_tests/port/factory.py
WebKitTools/Scripts/webkitpy/layout_tests/port/passing.py [deleted file]
WebKitTools/Scripts/webkitpy/layout_tests/run_webkit_tests_unittest.py