...
- is the quality increasing? Put another way: will bugs in mature parts of the system be decreasing with time?
- are we on the right track to increasing quality?
- how can we improve?
We didn't get to these questions as much, though we do have ideas for improvement and action items
Two areas
Regressions:
- Pawel feels like the high number of UI refactors is largely contributing to the half of bugs which are regressions.
- a more functional testing approach in the UI might help
- product testing in the middle of a sprint is a bad idea as the changes are in-flight
- refactors are exacerbating this
...
- How do we refactor (which has caused bugs), and do product level testing in a sprint?
- sprint shuffle - one on refactors, the next not
- label tickets as refactors so that QA testing can see which ones are in-flight
- increase the release cycle (momentarily decreases bug finding priority)
- freeze ui compontents docker image - use versioning to take it off the CD server (test). Need to solve for how QA tests the snapshot?
- hit list of UI refactor targets (we have: UI UX backlog in confluence)
- how do we get edge cases in tickets? i.e. how do we get developers to test the right edge cases in-flight?
- VR could be more specific
- Developer could be more specific
- having a time to add edge cases focuses the developer to first think about what the edge cases are (4 - the whole group)
- haven't been doing estimation meetings as much recently - we could hold these, and have the group brainstorm
Action items
- Nick Reid (Deactivated) to try the UI approach (decorator) on Product Grid Cell in his private repo, share in tech forum, and re-share next committee call
- Paweł Gesek to hold some meetings to groom out the edge cases
- Nick Reid (Deactivated) and Mary Jo Kochendorfer (Deactivated) to meet about sprint shuffle idea to prevent regressions in UI