Confirmed users
753
edits
(first draft of treeclosures) |
(Adding in breakdown of closures) |
||
| Line 8: | Line 8: | ||
= Tree Closures = | = Tree Closures = | ||
Tree Closures for a number of the integration branches are currently on the rise. We can see this on [http://futurama.theautomatedtester.co.uk Futurama]. Some of the current tree closures can be attributed to the length that tests take to run (Normalising test run length would solve this). | Tree Closures for a number of the integration branches are currently on the rise. We can see this on [http://futurama.theautomatedtester.co.uk Futurama]. Some of the current tree closures can be attributed to the length that tests take to run (Normalising test run length would solve this). | ||
For this year, the amount of tree closures have been attributed to the following | |||
{| class="wikitable" | |||
|- | |||
! Tree Closed for a Test or Bustage !! Count | |||
|- | |||
| Failing Test - No Try run done || 7 | |||
|- | |||
| Try breadth of run not sufficient || 3 | |||
|- | |||
| Bustage - No Try Run || 5 | |||
|- | |||
| Bustage - Try breadth of run not sufficient || 3 | |||
|- | |||
| Perf Regression || 1 | |||
|} | |||
= Developer Experience = | = Developer Experience = | ||