diff options
| author | kelvinp@chromium.org <kelvinp@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-18 00:06:39 +0000 |
|---|---|---|
| committer | kelvinp@chromium.org <kelvinp@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-18 00:06:39 +0000 |
| commit | f4e0bd2cbf194d9a59fd88a3a255d8676ad2406f (patch) | |
| tree | 116d4e4fd3472dad3a9b56f861f5c104dd4f7ef9 /chrome/js_unittest_rules.gypi | |
| parent | e2be10e34a5209ca4d1bad89b7465f2e614f6f90 (diff) | |
| download | chromium_src-f4e0bd2cbf194d9a59fd88a3a255d8676ad2406f.zip chromium_src-f4e0bd2cbf194d9a59fd88a3a255d8676ad2406f.tar.gz chromium_src-f4e0bd2cbf194d9a59fd88a3a255d8676ad2406f.tar.bz2 | |
Retire gtestjs unit tests
Now that the QUnit-based unit tests are running on the bots, we can retire gtestjs unit tests.
This CL
1. Modifies remoting_webapp_unittest to include all files that are formerly covered by all_js_load.gtestjs.
2. Removes all the gtestjs files under remoting.
3. Moves run_all_remoting_unittests.cc back into the remoting directory as we no longer depends on chrome_paths.h.
Review URL: https://codereview.chromium.org/394023002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283941 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/js_unittest_rules.gypi')
| -rw-r--r-- | chrome/js_unittest_rules.gypi | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/chrome/js_unittest_rules.gypi b/chrome/js_unittest_rules.gypi index d877f16..27901f1c 100644 --- a/chrome/js_unittest_rules.gypi +++ b/chrome/js_unittest_rules.gypi @@ -26,8 +26,6 @@ # Note that when you run your TestSuite, you'll need to call # chrome::RegisterPathProvider(). These path providers are required by # src/chrome/test/base/v8_unit_test.cc to setup and run the tests. -# -# See src/chrome/test/base/run_all_remoting_unittests.cc for an example. { 'dependencies': [ |