Confirmed users
3,376
edits
ReleaseEngineering/How To/Validate a New Config: Difference between revisions
ReleaseEngineering/How To/Validate a New Config (view source)
Revision as of 19:03, 22 February 2019
, 22 February 2019→Greening up: a
(initial outline) |
(→Greening up: a) |
||
| Line 29: | Line 29: | ||
One word of caution here is that the browser is a changing environment every day. We change features, fix things, break things, and most importantly our tests are changing daily as well. So what failures you found yesterday might not be the same failures you see today. Typically I view this as a 3 pass process: | One word of caution here is that the browser is a changing environment every day. We change features, fix things, break things, and most importantly our tests are changing daily as well. So what failures you found yesterday might not be the same failures you see today. Typically I view this as a 3 pass process: | ||
1) get jobs to schedule, basic tools to work (1 week) | 1) get jobs to schedule, basic tools to work (1 week) | ||
2) push, file bugs, resolve issues (3 weeks) | 2) push, file bugs, resolve issues (3 weeks) | ||
3) push, confirm fixed bugs, file new bugs (2 weeks) | 3) push, confirm fixed bugs, file new bugs (2 weeks) | ||
4) push, confirm fixed bugs, file new bugs (2 weeks) | 4) push, confirm fixed bugs, file new bugs (2 weeks) | ||
Once you get to a more stable state, then it is waiting on a small number of bugs to be resolved and often you can start running the tests as tier-3 or tier-2 with the tests/jobs disabled until the bugs are fixed. This is not a good idea until at least the 3rd or 4th cycle in greening up. | Once you get to a more stable state, then it is waiting on a small number of bugs to be resolved and often you can start running the tests as tier-3 or tier-2 with the tests/jobs disabled until the bugs are fixed. This is not a good idea until at least the 3rd or 4th cycle in greening up. | ||
= Validate the config = | = Validate the config = | ||