Retire gtestjs unit tests

chrome/js_unittest_rules.gypi

Index: chrome/js_unittest_rules.gypi
diff --git a/chrome/js_unittest_rules.gypi b/chrome/js_unittest_rules.gypi
index d877f16862d1effbb1278860b15449f161d896c3..27901f1c104dcef7e7a555cea8da22ea637089ae 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.

[garykac, 2014/07/15 23:23:42]

Can js_unittest_rules.gypi and js_unittest_vars.gypi be removed entirely?

You may want to check in the remoting/... changes first and do the chrome/
cleanup in a separate cl.

Also, if this file sticks around, it should direct people to the new way to do
JS unittests rather than having all this misleading content.

[kelvinp, 2014/07/16 00:17:55]

Unfortunately, I can't remove js_unittest_rules.gypi and js_unittest_vars.gypi
as there are other tests in chrome still depend on gtestjs.
I think I will leave this CL open for a few days.  If I didn't get approval from
owners of this file, then I will just check-in the chromoting part first.
Eventually, I will advertise the QUnit framework on dev.chromium.org.  I already
have a page going, http://dev.chromium.org/javascript-unittests.  So far, I only
got instructions about how to add test cases to an existing test suite.  Once I
got instructions to add new test suite, I will link it to the main page.

 
 {
     'dependencies': [