2019-09-30 - Triage report for "group::testing"
Hi, @jheimbuck_gl @erushton @jhampton
This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:
- Determine if the issue should be closed if it is no longer relevant or a duplicate.
- If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.
Feature Proposal Section
For the following feature proposals. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
feature with customer
Unscheduled-
#32310 (confidential) ~"(confidential)"
feature (non-customer)
Unscheduled-
#32566 Parallelize system testing using minikube Category:System Testing, devopsverify, documentation, feature, grouptesting -
#6284 Enforce code coverage % before merge Create [DEPRECATED], Enterprise Edition, auto updated, devopsverify, feature, grouptesting, merge requests, pipeline, potential proposal, test
Bug Section
For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.
Heatmap for all bugs
Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.
~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 4 | 0 | 0 | 0 |
~P3 | 0 | 0 | 9 | 0 | 0 |
~P4 | 0 | 0 | 1 | 3 | 0 |
~"No priority" | 0 | 0 | 1 | 0 | 1 |
Unscheduled ~bug (non-customer)
-
#31981 (closed) Code Quality results no longer appear in merge request Category:Code Quality, ~"bug", devopsverify, grouptesting -
#31975 Junit report displays/counts multiple tests as one test Category:Continuous Integration, ~"S3", ~"bug", devopsverify, grouptesting
Heatmap for ~missed-SLO bugs
~S1 | ~S2 | ~S3 | ~S4 | |
---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 |
~P2 | 0 | 3 | 0 | 0 |
~P3 | 0 | 0 | 0 | 0 |
~P4 | 0 | 0 | 0 | 0 |
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook: