GitLab Pipeline Insights Group, 20 Apr 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Verify:Testing 14.0 Milestone Refinement kickof

Description

Walkthrough of the 14.0 planning issue focusing on the theme of the milestone and some issues that need attention during the refinement phase: https://gitlab.com/gitlab-org/ci-cd/testing-group/-/issues/49

A

Hey team: uh this is the 14-0 uh planning or refinement rather kickoff uh for the verified testing team. I have up and I'm sharing the 14-0 planning issue, which I just did some refinement on myself. This milestone kicks off, may 22nd goes through the 21st for the 622 release.

A

You can see our capacity, how we're trending uh doing pretty well, uh but I'm going to dig in the milestone theme for this in this milestone.

A

This is a major we're going to enable all teams to enforce test coverage requirements through merge, request approvals, so we're going to use that existing mechanism so that this is available for all tiers core being a optional merge request approval if test coverage is set up, that it shouldn't be able to decrease, it has to stay or increase for a merge request to merge as the result on the branch and then we're also going to focus on delivering breaking changes that we've previously communicated renaming the default browser, performance, testing, job and updating the default code.

A

Climate robocop engine that'll break some support for some older versions of ruby. I wanted to call out a couple other issue types. As we start, our refinement, the four bugs that I have right now, scheduled into the milestone, the code quality and mr widget status of the port not being taken into account. This is a bug that we found as we were vetting the new code quality mr diff work, so this should improve when we show that there's no code, quality issues found versus no report found make that user experience a little bit better.

A

The code quality issue with docker hub rate limits. We've kicked this out a couple of milestones now, so let's dig in and figure out what our next minimum viable changes here, even if it's documentation, so we can start to make some better traction on this. For the users test report api not being consistent, we're using a jquery endpoint as opposed to loading up results of the report itself uh in two different places.

A

So the experience isn't exactly the same, so we'll get that consistent and then the last one here this code, climate, widget struggles or the code quality rather which it struggles with big json files. As we move that comparison into the backend, I want to take a look and see if that's still the case, so we should be able to replicate some really big.

A

You know 20 30, meg, json files and have them loaded up and compare them in the back end see if there's still that struggle on the front end slow loading, technical debt issues, we only have one feature: maintenance issue. So far, it's a follow-up to the community contribution adjusting the badge key text. So as we identify more, let's get those tagged to get to our target of 20 of our velocity is future maintenance issues and then a couple of the user experience debt issues.

A

The test report screen doesn't work well with matrix ids or when using matrix builds. Miranda, I think, did a great job identifying an mvc to fix that experience. That will apply to both the test, summary widget and the test report.

A

So that's great and then our next iteration cleaning up the code quality, mr widget, so that things are grouped a little bit better, and this is we've already sorted by severity, which is a great iteration for us next, within that we're going to then sort by file itself so that you can see all of the criticals or majors or minors whatever it is by file so that as you're digging into one you're, not hunting around through the list.

A

Looking for all of the things that you can address in that file is just a single chunk of stuff that you can pay attention to. So that is where we're at in the refinement. Today we don't have okr alignment as we're still sorting those out for the quarter ourselves, but as soon as those are there I'll put them in so start, taking a look scrolling through these issues. The link to the board is there, so you can get in and start looking at stuff ping me with questions or ask in slack thanks.