Changes between Version 4 and Version 5 of RebaselineServer


Ignore:
Timestamp:
Dec 6, 2010, 3:02:49 PM (14 years ago)
Author:
mihaip@chromium.org
Comment:

Rebaseline server: rest of UI walkthrough

Legend:

Unmodified
Added
Removed
Modified

  • RebaselineServer

    v4 v5  
    33The "Rebaseline Server" is a tool that makes it easy to do "mass" rebaselines (updating of pixel or text baselines for dozens or hundreds of layout tests). It makes it easy to review changes to baselines and update existing ones (and optionally move them, to handle OS transitions). It's known as a ''server'' because it runs a local HTTP server which makes it easy to have a cross-platform GUI for reviewing that is backed by Python code for doing the SCM (SVN/Git) operations on the filesystem.
    44
    5 To use the tool, run:  `webkit-patch rebaseline-server WebKitBuild/{Debug|Release}/layout-test-results` (after having run `new-run-webkit-tests`). See [#SampleUsages sample usages] below for more details.
     5To use the tool, run:  `webkit-patch rebaseline-server WebKitBuild/{Debug|Release}/layout-test-results` (after having run `new-run-webkit-tests`). Once the GUI that runs at http://localhost:8127 launches, you can inspect results and add tests that you wish to rebaseline to the queue. Once you have enqueued enough tests, you can process the queue, which will do the necessary Git/SVN operations. You can then submit those changes as usual with `webkit-patch`.
     6
     7See [#UIWalkthrough UI walkthrough] [#SampleUsages sample usages] below for more details.
    68
    79== UI Walkthrough ==
    … …  
    1719=== 2. Image results ===
    1820
    19 Shows expected/actual/diff of the image results (if the test failed because of image diffs). The diff displays pixels that were the same at 25% opacity, and different ones as red. You can click on any image to use the [#Loupe loupe] to magnify that area. In the case of matching images but mismatching checksums, the diff area displays the checksums.
     21Shows expected/actual/diff of the image results (if the test failed because of image diffs). The diff displays pixels that were the same at 25% opacity, and different ones as red. You can click on any image to use the [#a4.Loupe loupe] to magnify that area. In the case of matching images but mismatching checksums, the diff area displays the checksums.
    2022
    2123=== 3. Text results ===
    … …  
    2426
    2527=== 4. Loupe ===
     28
     29[[Image(section-4.png)]]
     30
     31The loupe is triggered by clicking in any of the image outputs. It shows enlarged areas of the expected, actual and diff images of 20x20 pixels around the click point. The color values at the click point are also displayed. You can also click within enlarged pixels in the loup to re-center it on that pixel.
     32
     33=== 5. Test state ===
     34
     35A test can either need rebaselining, be in the rebaseline queue, have its rebaseline attemp succeed or fail. The current state of it is shown in the lower left part of the footer. The list of tests in the test selector is also grouped by test state.
     36
     37=== 6. Current baselines ===
     38
     39The currently checked in baselines (for all platforms) are listed in the footer as well. The baselines that were actually used for the test are in brighter blue (and are bold).
     40
     41=== 7. Baseline target (and what to do with existing baselines) ===
     42
     43The first platform drop-down lets you choose which platform you want to update baselines for (e.g. `mac` or `chromium-linux`). The second one lets you choose what to do with existing baselines (if any) for that platform. This is useful when updating baselines because of OS changes, in which case existing baselines need to be moved to a more version-specific directory (e.g once Snow Leopard was released, the `mac` directory should contain Snow Leopard baselines, and existing ones were moved to `mac-leopard`).
     44
     45=== 8. Queue ===
     46
     47[[Image(section-8.png)]]
     48
     49Rebaselining is not done immediately (since the SCM operations can take a while). Instead, tests to be rebaselined are added to a queue (using the big button in the lower right). The queue can be shown and managed by using the "Queue" link next to it. To actually rebaseline the queue, the button under it should be used.
     50
     51=== 9. Other links ===
     52
     53The "Log" link in the upper right lets you see log output from the server during a rebaseline. This may be helpful in understanding what operations are run as part of a rebaseline. Next to it is an "Exit" link that shuts down the local HTTP server.
    2654
    2755=== Keyboard shortcuts ===