Changes between Version 18 and Version 19 of Rebaseline

Timestamp:

Jun 3, 2012 9:18:08 PM (12 years ago)

Author:

rniwa@webkit.org

Comment:

Update per TestExpectations rename

Rebaseline

@@ -11 +11 @@
   * Extract baselines from the archive file for all identified files.
   * Add new baselines to SVN or Git repository.
-  * For each test that has been rebaselined, remove this platform option from the test in _test_expectation.txt_. If no other platform options remaining after removal, delete the test from the file.
+  * For each test that has been rebaselined, remove this platform option from the test in [wiki:TestExpectations TestExpectations files]. If no other platform options remaining after removal, delete the test from the file.
 
 After new baselines are generated, the tool launches a html page to compare the old and new baselines. (EDIT: No it doesn't. See https://lists.webkit.org/pipermail/webkit-dev/2011-November/018527.html ) The html can be disabled with `--no_html_results` option.
@@ -17 +17 @@
 == How to use it? ==
   * Make sure the test files exist in repository and the build bots have cycled at least once after they were committed. If you are not sure, check the Release version of [http://build.chromium.org/buildbot/layout_test_results/ buildbot layout archive] to see whether your test results are available. By default, the rebaselining tool retrieves new baselines from the release version of buildbot layout test archive. 
-  * Update `test_expectations.txt`: add flag `REBASELINE` to the tests that need to be rebaselined.
+  * Update `TestExpectations`: add flag `REBASELINE` to the tests that need to be rebaselined.
   * Run rebaselining script: `Tools/Scripts/webkit-patch rebaseline-expectations`
-  * If the script runs successfully, new baselines (expected files) are added to SVN repository and the rebaselined tests are removed from `test_expectations.txt`.
+  * If the script runs successfully, new baselines (expected files) are added to SVN repository and the rebaselined tests are removed from `TestExpectations`.
   * The tool launches a html page to compare the old and new baselines. (EDIT: No it doesn't. See https://lists.webkit.org/pipermail/webkit-dev/2011-November/018527.html ) Check the new baseline changes are expected.
-  * Prepare a patch with the new baselines and `test_expectations.txt`, review the changes and then commit the patch.
+  * Prepare a patch with the new baselines and `TestExpectations`, review the changes and then commit the patch.
 
 == Examples ==
@@ -27 +27 @@
 
   * If these are tests just added, make sure the layout tests ran at buildbot and the test results have been archived. 
-  * Update `test_expectations.txt` to include the following lines:
+  * Update `TestExpectations` to include the following lines:
 {{{
 BUG1234 REBASELINE : foo1.html = FAIL
@@ -34 +34 @@
 
   * Run `Tools/Scripts/webkit-patch rebaseline-expectations`.
-  * Check that tests `foo1` and `foo2` were removed from test_expectations.txt.
+  * Check that tests `foo1` and `foo2` were removed from TestExpectations.
 
   * Create a patch, review the changes and commit.