Changes between Version 9 and Version 10 of NewRunWebKitTests

Timestamp:

Jul 12, 2011, 6:44:13 PM (13 years ago)

Author:

dpranke@chromium.org

Comment:

--

NewRunWebKitTests

@@ -73 +73 @@
  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.
 
+== Commonly used Command Line Flags ==
+
+NRWT supports a ''lot'' of flags. Here are some of the most popular:
+
+|| || --platform || the platform to run (e.g., "chromium-mac", "win-wk2", etc. ||
+|| || --debug || use the Debug configuration ||
+|| || --release || use the Release configuration ||
+|| -n || --dry-run || dry-run ... do everything but actually run the tests ||
+|| -p || --pixel-tests || run with pixel-tests enabled ||
+|| || --no-new-test-results || don't create any new test results for new tests (NRWT will create them by default ||
+|| || --no-show-results || don't display the summary HTML file in a web browser at the end of the run ||
+
 == More Advanced Scenarios ==
+
+
+
+===  A recommended set of command-line flags ===
+
+dpranke@chromium.org has spent a lot of time hacking on NRWT. The command line argument he most frequently uses are: 
+
+{{{
+% new-run-webkit-tests --clobber-results --no-new-test-results --no-show-results --no-retry-failures --print config,default 
+}}}