| OLD | NEW |
| 1 # Chromium Recipes: Reference Doc | 1 # Chromium Recipes: Reference Doc |
| 2 | 2 |
| 3 [TOC] | 3 [TOC] |
| 4 | 4 |
| 5 ## I just want to.... | 5 ## I just want to.... |
| 6 | 6 |
| 7 This section covers common tasks for chromium developers. If you want a more | 7 This section covers common tasks for chromium developers. If you want a more |
| 8 full background on the chromium recipes, go to the [Background](#Background) | 8 full background on the chromium recipes, go to the [Background](#Background) |
| 9 section. | 9 section. |
| 10 | 10 |
| (...skipping 127 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 138 | 138 |
| 139 "Linux Builder": { | 139 "Linux Builder": { |
| 140 "gtest_tests": [ | 140 "gtest_tests": [ |
| 141 { | 141 { |
| 142 "test": "base_unittests" | 142 "test": "base_unittests" |
| 143 }, | 143 }, |
| 144 ... | 144 ... |
| 145 ] | 145 ] |
| 146 } | 146 } |
| 147 | 147 |
| 148 Note that this relies on gtest generator in the bot configuration in the | |
| 149 `chromium_tests` module. For example, given the file [`scripts/slave/recipe_modu
les/chromium_tests/chromium_linux.py`](https://code.google.com/p/chromium/codese
arch#chromium/build/scripts/slave/recipe_modules/chromium_tests/chromium_linux.p
y) | |
| 150 , you would need: | |
| 151 | |
| 152 'Linux Builder': { | |
| 153 ... | |
| 154 'test_generators': [ | |
| 155 steps.generate_gtest, | |
| 156 ... | |
| 157 ], | |
| 158 ... | |
| 159 }, | |
| 160 | |
| 161 Changes to the JSON file can be tested on the trybots, and you can verify that | 148 Changes to the JSON file can be tested on the trybots, and you can verify that |
| 162 they take effect and build still passes. | 149 they take effect and build still passes. |
| 163 | 150 |
| 164 ### Add a new non gtest-based test | 151 ### Add a new non gtest-based test |
| 165 Generally, look at [steps.py](https://code.google.com/p/chromium/codesearch#chro
mium/build/scripts/slave/recipe_modules/chromium_tests/steps.py) | 152 Generally, look at [steps.py](https://code.google.com/p/chromium/codesearch#chro
mium/build/scripts/slave/recipe_modules/chromium_tests/steps.py) |
| 166 , and either use an existing class there, or add a new one. | 153 , and either use an existing class there, or add a new one. |
| 167 | 154 |
| 168 ## Background | 155 ## Background |
| 169 Chromium tests are currently run on buildbot, and are organized by builders. | 156 Chromium tests are currently run on buildbot, and are organized by builders. |
| 170 A builder, in buildbot’s terminology, is a sequence of steps | 157 A builder, in buildbot’s terminology, is a sequence of steps |
| (...skipping 153 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 324 Path: [build/scripts/slave/recipe_modules/chromium_tests/api.py](https://code.go
ogle.com/p/chromium/codesearch#chromium/build/scripts/slave/recipe_modules/chrom
ium/api.py) | 311 Path: [build/scripts/slave/recipe_modules/chromium_tests/api.py](https://code.go
ogle.com/p/chromium/codesearch#chromium/build/scripts/slave/recipe_modules/chrom
ium/api.py) |
| 325 | 312 |
| 326 Implements methods like `configure_build`, `prepare_checkout`, compile, etc. | 313 Implements methods like `configure_build`, `prepare_checkout`, compile, etc. |
| 327 that take configuration parameters and actually run the steps. | 314 that take configuration parameters and actually run the steps. |
| 328 | 315 |
| 329 ### src/testing/buildbot/*.json: per-master configs: targets & tests | 316 ### src/testing/buildbot/*.json: per-master configs: targets & tests |
| 330 | 317 |
| 331 Example config: [src/testing/buildbot/chromium.mac.json](https://code.google.com
/p/chromium/codesearch#chromium/src/testing/buildbot/chromium.mac.json&sq=packag
e:chromium) | 318 Example config: [src/testing/buildbot/chromium.mac.json](https://code.google.com
/p/chromium/codesearch#chromium/src/testing/buildbot/chromium.mac.json&sq=packag
e:chromium) |
| 332 | 319 |
| 333 These configs live in the project repo, and define additional compile targets an
d specific tests to run on each builder. | 320 These configs live in the project repo, and define additional compile targets an
d specific tests to run on each builder. |
| OLD | NEW |