Add local results details pages.

build/android/pylib/base/test_run.py

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 
 class TestRun(object):
   """An execution of a particular test on a particular device.
 
   This is expected to handle all logic that is specific to the combination of
   environment and test type.
 
   Examples include:
     - local gtests
     - local instrumentation tests
   """
 
-  def __init__(self, env, test_instance):
+  def __init__(self, env, test_instance, test_output_saver):
     self._env = env
     self._test_instance = test_instance
+    self._test_output_saver = test_output_saver

[jbudorick, 2017/06/20 14:12:54]

Can you explain why this is in the test run rather than the environment?

[mikecase (-- gone --), 2017/07/10 17:11:10]

Well, I think test_runs are really the things saving test results. The output
you save isnt tied to whether you are running tests on your Workstation or on
Android devices, it depends on what test you are running.

Counterpoint, is that regardless of test_run you probably will always use the
same type of output_saver. Really doesnt matter where it lives. Moving to
environment since it might be simpler.

 
   def TestPackage(self):
     raise NotImplementedError
 
   def SetUp(self):
     raise NotImplementedError
 
   def RunTests(self):
     """Runs Tests and returns test results.
 
     Returns:
       Should return list of |base_test_result.TestRunResults| objects.
     """
     raise NotImplementedError
 
   def TearDown(self):
     raise NotImplementedError
 
   def __enter__(self):
     self.SetUp()
     return self
 
   def __exit__(self, exc_type, exc_val, exc_tb):
     self.TearDown()