Chromium Code Reviews| Index: base/test/test_switches.cc |
| diff --git a/base/test/test_switches.cc b/base/test/test_switches.cc |
| index 79fbad12fd6dc9288fb80b020b008dd41b3941b0..798386eaeff79488744735e662bf8027f42be4d0 100644 |
| --- a/base/test/test_switches.cc |
| +++ b/base/test/test_switches.cc |
| @@ -4,9 +4,21 @@ |
| #include "base/test/test_switches.h" |
| +namespace switches { |
| + |
| +// Run the tests and the launcher in the same process. Useful for debugging a |
| +// specific test in a debugger. |
| +const char kSingleProcessTestsFlag[] = "single_process"; |
| + |
| +// Run the tests and the launcher in the same process, and Chromium in single |
|
Paweł Hajdan Jr.
2012/06/22 07:52:42
This is not true. It runs Chrome in single-process
Scott Byer
2012/06/22 22:02:55
Done.
|
| +// process mode. |
| +const char kSingleProcessTestsAndChromeFlag[] = "single-process"; |
| + |
| // Time (in milliseconds) that the tests should wait before timing out. |
| // TODO(phajdan.jr): Clean up the switch names. |
| -const char switches::kTestLargeTimeout[] = "test-large-timeout"; |
| -const char switches::kTestTinyTimeout[] = "test-tiny-timeout"; |
| -const char switches::kUiTestActionTimeout[] = "ui-test-action-timeout"; |
| -const char switches::kUiTestActionMaxTimeout[] = "ui-test-action-max-timeout"; |
| +const char kTestLargeTimeout[] = "test-large-timeout"; |
| +const char kTestTinyTimeout[] = "test-tiny-timeout"; |
| +const char kUiTestActionTimeout[] = "ui-test-action-timeout"; |
| +const char kUiTestActionMaxTimeout[] = "ui-test-action-max-timeout"; |
| + |
| +} // namespace switches |