[telemetry] Script for finding all Telemetry dependencies.

tools/telemetry_tools/find_dependencies_unittest.py

Index: tools/telemetry_tools/find_dependencies_unittest.py
diff --git a/tools/telemetry/telemetry/core/timeline/event_unittest.py b/tools/telemetry_tools/find_dependencies_unittest.py
old mode 100644
new mode 100755
similarity index 60%
copy from tools/telemetry/telemetry/core/timeline/event_unittest.py
copy to tools/telemetry_tools/find_dependencies_unittest.py
index 2c80c32146bb8c52ecb460142ac81c5bc5b7d340..5029daad7968082dbbee0d5e12cd38efab4624f8
--- a/tools/telemetry/telemetry/core/timeline/event_unittest.py
+++ b/tools/telemetry_tools/find_dependencies_unittest.py
@@ -1,8 +1,15 @@
+#!/usr/bin/env python

[tonyg, 2014/01/29 05:10:08]

Not necessary, right?

We should definitely get these unittests into tools/telemetry/telemetry so that
tools/telemetry/run_tests will run them. Otherwise, we'll have to go through a
big ordeal to get them running on the bots.

[dtu, 2014/02/13 21:49:35]

I kind of think I would like all unit tests to have a __main__. It's more
natural to people who are familiar with Python, but new to Telemetry.

 # Copyright (c) 2013 The Chromium Authors. All rights reserved.

[tonyg, 2014/01/29 05:10:08]

2014

[dtu, 2014/02/13 21:49:35]

Done.

 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
+import os
 import unittest
 
-class TimelineEventTest(unittest.TestCase):
+
+class FindDependenciesTest(unittest.TestCase):

[tonyg, 2014/01/29 05:10:08]

For this test, why not just create a mini, fake telemetry directory with, say
one Measurement and PageSet, etc. Then run it against that directory.

[dtu, 2014/02/13 21:49:35]

I think I will make unit tests in a followup patch. We need to move these files
and the bootstrap into tools/telemetry/ before it's unit-testable.

   pass
+
+
+if __name__ == '__main__':
+  unittest.main()