History log of /frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
34f3851e9534b19ab0f02d3eb11f52ddb2635530 20-Sep-2010 Steve Block <steveblock@google.com> Fix DumpRenderTree2 to make AbstractResult serializable

This should have been doen as part of
https://android-git.corp.google.com/g/#change,65283

Change-Id: I7a4681f98014ff5a7546a7346fc5523e01f62e19
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java
394e0fb84996f5f5ee9e33c9e2f0e11066e6f943 17-Sep-2010 Maksymilian Osowski <maxosowski@google.com> Updated Summarizer to use SQLite DB.

It avoids OOM issues by dumping the memory to the DB every
few hundred tests and then reading them in chunks when
generating summaries, etc.

Change-Id: I5f63d960d456f17e9f2189230a7ae0ca5607ce51
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java
8a6def02473ee4fbffcd1b34173daf751d316202 17-Sep-2010 Steve Block <steveblock@google.com> Update DumpRenderTree2 to handle failing tests where no meaningful diff is available

Currently, DumpRenderTree2 asigns the following result codes
{PASS, FAIL_RESULT_DIFFERS, FAIL_NO_EXPECTED_RESULT, FAIL_TIMED_OUT,
FAIL_CRASHED}

This is not strictly correct, as a test may fail for any of three
reasons - crashing, timing out, or the the result not being as
expected. Therefore, it's possible for a test to fail even if the
result is as expected.

This patch updates AbstractResult to handle each of the three reasons
for failure separately. We then test all three to determine if the
test has passed.

This allows us to correctly report whether or not the result differs
from expected for a failing test.

Change-Id: I7adcfe72c4dd0bd3de2e1b868d9807be6eb5bddf
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java
01c1f9d9e9e7ab3a40a9bf27195a434eb0c9bb9b 02-Sep-2010 Maksymilian Osowski <maxosowski@google.com> The results now show which expected result was used.

Bug: 2889857
Change-Id: If2b7e6e6a22ddb5db6c6a50a358e8f263914e6c0
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java
dd4bff62b54033bedc254f517397ae8f954d0dc9 30-Jul-2010 Maksymilian Osowski <maxosowski@google.com> First batch of layoutTestController functions + some fixes and tweaks.

Change-Id: I9dae192c498d8e19fd75861a1a6cf1f079ad9c6f
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java
6d0dae6a6534a01ee4c58d4f4ee1bf115c82319c 27-Jul-2010 Maksymilian Osowski <maxosowski@google.com> Upgraded DRT2 to generate nice HTML summaries of the tests.

Change-Id: Ibe4ee3af30fe20aeab2f3fed9c4c5693c9a0f268
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java
5f0ccd76a88586ce85c17cb4db058934e693a4fc 23-Jul-2010 Maksymilian Osowski <maxosowski@google.com> Moved practically all of the prerefactoring functionality to the new design.

Renamed LayoutTestsRunner activity to TestsListActivity. It will be responsible for restrating the Executer after the crash. Now it only starts
it.
Renamed LayoutTestsRunnerThread to TestsListPreloaderThread. It only preloads tests now.
LayoutTest class is no longer needed, its functionality is in LayoutTestsExecuter.
Most of the functionality from LayoutTestsRunnerThread is now in ManagerService.

Change-Id: I08924d949ceb9f8816888bc8e795256d0542fa99
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java
7ddc0b7a72aa66d699fecce3d855a6c70f844647 22-Jul-2010 Maksymilian Osowski <maxosowski@google.com> First stage of refactoring the code to handle crashes gracefully.

There is a new activity (LayoutTestsExecuter) added that is responsible for acutally running the tests and sending the actual results to the new
ManagerService class. This class will take over most of the functionality of the current LayoutTestsRunnerThread. At the moment
LayoutTestsRunnerThread is changed so that after computing the tests' list it sends the list to LayoutTestsExecuter. The rest of the code is
never called. It will be shifted to the service.

Current implementation of ManagerService only prints the log message on receiving the bundle with actual results from LayoutTestsExecuter.

Change-Id: I5adcbc20bb18ebf24324974bc66e4b31c4b81902
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java
4ee7f4b19489f4dc9b87e90d1e5c7742cfa7ebe0 16-Jul-2010 Maksymilian Osowski <maxosowski@google.com> LayoutTest class with supporting classes (AbstractResult, TextResult).

These classes are responsible for actually running the tests, checking the results, generating visual diffs, etc.

Change-Id: I9b7f554409db1c97ac086c456db3aea3b993b5c6
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java
3c8ccb384513dd9bae0f98ac516ea36fbaa3173b 12-Jul-2010 Maksymilian Osowski <maxosowski@google.com> Added the LayoutTestsRunner class that is responsible for running the tests. Also, added some methods to FileFilter.

It preloads the tests from the given path, runs them and asks for dumps and diffs. It will also prepare summaries in the future. It delegates
most of the work of actually running the individual tests to LayoutTest class and AbstractResult (and its subclasses in the future).

Change-Id: I483bf26a380b539e4769e61b4a09fa270ab0e8e9
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/AbstractResult.java