Changes between Version 9 and Version 10 of NewRunWebKitTests


Ignore:
Timestamp:
Jul 12, 2011 6:44:13 PM (8 years ago)
Author:
dpranke@chromium.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NewRunWebKitTests

    v9 v10  
    7373 3. The test that failed and the type of test failure that happened are displayed in such a way as to be directly copied into the [wiki:TestExpectations test_expectations.txt] file.
    7474
     75== Commonly used Command Line Flags ==
     76
     77NRWT supports a ''lot'' of flags. Here are some of the most popular:
     78
     79|| || --platform || the platform to run (e.g., "chromium-mac", "win-wk2", etc. ||
     80|| || --debug || use the Debug configuration ||
     81|| || --release || use the Release configuration ||
     82|| -n || --dry-run || dry-run ... do everything but actually run the tests ||
     83|| -p || --pixel-tests || run with pixel-tests enabled ||
     84|| || --no-new-test-results || don't create any new test results for new tests (NRWT will create them by default ||
     85|| || --no-show-results || don't display the summary HTML file in a web browser at the end of the run ||
     86
    7587== More Advanced Scenarios ==
     88
     89
     90
     91===  A recommended set of command-line flags ===
     92
     93dpranke@chromium.org has spent a lot of time hacking on NRWT. The command line argument he most frequently uses are:
     94
     95{{{
     96% new-run-webkit-tests --clobber-results --no-new-test-results --no-show-results --no-retry-failures --print config,default
     97}}}