Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(81)

Side by Side Diff: media/tools/layout_tests/README

Issue 14316009: Update tools to reflect movement of TestExpectations (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Fix equality test Created 7 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | media/tools/layout_tests/test_expectations.py » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 Layout test analyzer script. 1 Layout test analyzer script.
2 2
3 * Prerequisite: 3 * Prerequisite:
4 4
5 This script requires PySVN (http://pysvn.tigris.org/) to be installed on the 5 This script requires PySVN (http://pysvn.tigris.org/) to be installed on the
6 machine. 6 machine.
7 7
8 * How to execute 8 * How to execute
9 9
10 python layouttest_analyzer.py (Please run with '-h' for available command-line 10 python layouttest_analyzer.py (Please run with '-h' for available command-line
(...skipping 41 matching lines...) Expand 10 before | Expand all | Expand 10 after
52 52
53 ** LayoutTests: 53 ** LayoutTests:
54 54
55 A class to store test names in layout tests. The test names (including 55 A class to store test names in layout tests. The test names (including
56 regular expression patterns) are read from a CSV file and used for 56 regular expression patterns) are read from a CSV file and used for
57 getting layout test names from Webkit SVN as well as test description. 57 getting layout test names from Webkit SVN as well as test description.
58 58
59 ** TestExpectations: 59 ** TestExpectations:
60 60
61 A class to model the content of test expectation file for analysis. 61 A class to model the content of test expectation file for analysis.
62 The raw test expectation file can be found in 62 The location of the test expectations file can be found in
63 |DEFAULT_TEST_EXPECTATION_LOCATION|. It is necessary to parse this 63 |TEST_EXPECTATIONS_LOCATIONS|. It is necessary to parse this
64 file and store meaningful information for the analysis (joining with 64 file and store meaningful information for the analysis (joining with
65 existing layout tests using a test name). Instance variable 65 existing layout tests using a test name). Instance variable
66 |all_test_expectation_info| is used. A test name such as 66 |all_test_expectation_info| is used. A test name such as
67 'media/video-source-type.html' is used for the key to store 67 'media/video-source-type.html' is used for the key to store
68 information. However, a test name can appear multiple times in the 68 information. However, a test name can appear multiple times in the
69 test expectation file. So, the map should keep all the occurrence 69 test expectation file. So, the map should keep all the occurrence
70 information. For example, the current test expectation file has the 70 information. For example, the current test expectation file has the
71 following two entries: 71 following two entries:
72 72
73 BUGWK58587 LINUX DEBUG GPU : media/video-zoom.html = IMAGE 73 BUGWK58587 LINUX DEBUG GPU : media/video-zoom.html = IMAGE
(...skipping 10 matching lines...) Expand all
84 period. 84 period.
85 85
86 ** TrendGraph: 86 ** TrendGraph:
87 87
88 A class to manage trend graph which is using Google Visualization 88 A class to manage trend graph which is using Google Visualization
89 APIs. Google Visualization API 89 APIs. Google Visualization API
90 (http://code.google.com/apis/chart/interactive/docs/gallery/annotatedtimeline. html) 90 (http://code.google.com/apis/chart/interactive/docs/gallery/annotatedtimeline. html)
91 is used to present the historical analyzer result. Currently, data 91 is used to present the historical analyzer result. Currently, data
92 is directly written to JavaScript file using file in-place 92 is directly written to JavaScript file using file in-place
93 replacement for simplicity. 93 replacement for simplicity.
OLDNEW
« no previous file with comments | « no previous file | media/tools/layout_tests/test_expectations.py » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698