Changes between Version 4 and Version 5 of NewRunWebKitTests


Ignore:
Timestamp:
Jul 7, 2011 3:00:51 PM (9 years ago)
Author:
dpranke@chromium.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NewRunWebKitTests

    v4 v5  
    1515== Running NRWT ==
    1616
    17 NRWT is designed to be run both directly by developers working in a terminal window, or by the buildbots. It supports a large number of command line options to customize the behavior and the output; only a few of the most commonly used options are mentioned here. The complete list of options is given by {{{new-run-webkit-tests --help}}} and {{{new-run-webkit-tests --help-printing}}}.
     17NRWT is designed to be run both directly by developers working in a terminal window, or by the buildbots. It supports a large number of command line options to customize the behavior and the output; only a few of the most commonly used options are mentioned here.
     18
     19The complete list of options is given by {{{new-run-webkit-tests --help}}} and {{{new-run-webkit-tests --help-printing}}}.
     20
     21=== Basic ===
     22
     23NRWT uses the concept of a "platform" to determine which WebKit port / implementation you are attempting to test. Where possible, it picks a default based on the operating system you are running on and the default configuration you have set (if any). However, sometimes you have to give it hints.
     24
     25By default, when run interactively in a terminal or console window, NRWT attempts to be fairly terse. It will display one line of output on screen, and update that in place with events as the test run occurs. If unexpected things happen (e.g., tests fails that aren't expected to fail), they are printed out as they happen, and then summarized again at the end. If everything passes, it will print a message saying so. Also, it returns the number of unexpected test failures in the exit code for the process.
     26
     27==== Examples ====
     28
     29Starting up initially
     30{{{
     31% new-run-webkit-tests
     32Collecting tests ...
     33}}}
     34
     35(this may take a few seconds, during which time other message may be displayed, like "checking build", "parsing expectations", etc. will be displayed.
     36
     37Eventually the tests will start running, and you'll get something resembling a progress meter:
     38
     39{{{
     40% new-run-webkit-tests
     41Testing (3%): 863 ran as expected, 0 didn't, 24080 left
     42}}}
     43
     44and when the test completes, you'll get output like:
     45
     46{{{
     47% new-run-webkit-tests
     48}}}
     49
     50=== More Advanced Scenarios ===