diff options
author | wez <wez@chromium.org> | 2015-03-12 09:19:19 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2015-03-12 16:19:45 +0000 |
commit | 0f92988f0ef745e9ea4b2ff68c897cb83d911469 (patch) | |
tree | 17105dd84ad04b3fd4553c52bdc8ab0cd3e22684 /remoting/remoting_webapp.gypi | |
parent | c5d2a79125d51665ec065be2481b2b54d8ca3895 (diff) | |
download | chromium_src-0f92988f0ef745e9ea4b2ff68c897cb83d911469.zip chromium_src-0f92988f0ef745e9ea4b2ff68c897cb83d911469.tar.gz chromium_src-0f92988f0ef745e9ea4b2ff68c897cb83d911469.tar.bz2 |
Move mocks and unittest JS files to sit alongside production code.
Chromium normally places unit-test implementations alongside the class
implementations, so that it's easy to see what has tests and what
doesn't.
Similarly placing mocks next to the corresponding interfaces or classes
makes it easier to spot and re-use them.
BUG=455972
Review URL: https://codereview.chromium.org/984203003
Cr-Commit-Position: refs/heads/master@{#320296}
Diffstat (limited to 'remoting/remoting_webapp.gypi')
-rw-r--r-- | remoting/remoting_webapp.gypi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/remoting/remoting_webapp.gypi b/remoting/remoting_webapp.gypi index 7b12553..d197e41 100644 --- a/remoting/remoting_webapp.gypi +++ b/remoting/remoting_webapp.gypi @@ -70,8 +70,8 @@ 'action_name': 'Verify remoting webapp unittests', 'inputs': [ '<@(remoting_webapp_crd_js_files)', - '<@(remoting_webapp_unittest_all_js_files)', - '<@(remoting_webapp_unittest_js_proto_files)', + '<@(remoting_webapp_unittests_all_js_files)', + '<@(remoting_webapp_unittests_js_proto_files)', ], 'outputs': [ '<(success_stamp_ut)', @@ -82,8 +82,8 @@ '--no-single-file', '--success-stamp', '<(success_stamp_ut)', '<@(remoting_webapp_crd_js_files)', - '<@(remoting_webapp_unittest_all_js_files)', - '<@(remoting_webapp_unittest_js_proto_files)', + '<@(remoting_webapp_unittests_all_js_files)', + '<@(remoting_webapp_unittests_js_proto_files)', ], }, ], # actions |