GitLab Pipeline Insights Group, 27 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Verify:Testing 13.7 Refinement kickoff

Description

The Verify:Testing team is going to do more async refinement for the 13.7 milestone. This is a walk through of the planning issue on Oct. 27, 2020 to identify key deliverable issues and bugs, items that need refinement and next steps for the team. This is just a point in time and the issue board is always our Single Source of Truth: https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group%3A%3Atesting&milestone_title=13.7

Planning Issue: https://gitlab.com/gitlab-org/ci-cd/testing-group/-/issues/20

A

Hey folks, I wanted to provide just a quick walk-through for the 13-7 planning issue, um as we kick off our refinement for 13-7 asynchronously in testing this time so trying that out. um Thank you, ricky for adding all the capacity. In the note um this uh this work is over the u.s holiday thanksgiving and is getting close to u.s holiday christmas or christmas holiday. um So we anticipate some reduced capacity on this milestone.

A

Some of the key issues or top priority deliverables that I have called out here are pipeline tab with screenshot links for failed tests. All the backend work is done for this. It's a front end only issue.

A

This is a popular issue, the parent issue, where we're going to end up with this, and it helps internal customers with their work. This is a top priority for a quality team of getting this, so they don't have to hunt through screenshots.

A

When a screenshot is captured on a failed test, they can just see those directly in the pipeline. The next top deliverable is the test history mvc, providing that in the full unit report. This is a continuation of the feature that we're going to start in actually 13-6 if there are a milestone here, I'll fix that um of taking that test history, the the mvc for that proving out that this is valuable data and then we can build on that in later milestones um and then, lastly, the front end or the customer facing features is graphing.

A

The average code coverage of all projects in a group. This is delivering that finishing delivery of that gitlab premium feature: that's going to drive an increase in our performance indicator, and this is a link out to the dashboard. So you can take a look so kind of following that theme on the performance indicator.

A

We have three tracking issues, all of them around paid features and all of them using usage pings that will get us both sas and self-managed, and it's really important for us to continue to track those and to keep building on this tracking so that we can see how we're doing increase that performance indicator number and also then track how new features are impacting that number over time.

A

So when I looked this morning, issues requiring refinement, we only have seven left awesome work so far, um there's already a chunk that have a weight on them. Thank you. So much uh specific back end things. I only see two that are labeled back end moving the code, quality comparison logic into the back end and then creating the partial report as a pipeline artifact for use in the code quality.

A

Mr widget, that's a change that we're making of where that gets, gets created and then the move code, quality comparison logic also has a front-end label on it. So sam and ricky, if you can take a look at those, I appreciate it.

A

Some user experience work, that's coming up. uh Vitica is going to be working on the design for adding a notice to the file header um in the mrdiff. This is our first step.

A

First, getting the code quality violations into the mrdiff inline, so we're taking one step and I think it'll be 13 8 or just adding a notice in the mrdif next to the file name, the code quality violations there and then the user can click that and see the widget same as they would on the mr and then after that, we'll have actually inline violations.

A

So that's being designed in thirteen seven, some active research projects that we have going on, I'm still working on code, category maturity scorecard. I anticipate that to probably bleed over into thirteen seven a little bit or trickle over into thirteen seven and the code quality job to be done. Research I'll also be kicking off, probably during thirteen seven um job to be done. Research for web browser, uh web browser performance testing and another of our categories probably usability.

A

I can't remember I'll stop my head um problem, validation, uh I'm still going back and forth on the code coverage reports. I think I just need to get that closed out and no solution. Validation happening in this milestone.

A

uh A couple of top bug fixes. uh We found out from a customer that the group code coverage report is only using the master of branch name, so we should be using whatever their default branch name is instead of that hard-coded one so that they can get data in that downloaded report and the code coverage on the project view. Probably on the group view as well, always shows a hard-coded window of three months of data.

A

We should actually have that reflect how much data there is, if possible, so debatable if that's a bug, fix or an enhancement um and then finally, okay, our alignment just want to talk through these real, quick, um so tracking paid features uh that set of three things: this maps up to one of the q4 products, okrs 100 of the devops groups, having a protected predicted paid gmail with instrumentation dashboards and quarterly targets. So this helps us move forward with that test. History, mvc that is going to help drive uh increase in stage monthly active users.

A

This is a key feature for us in getting users converted over from other ci solutions to gitlab ci graphing, the average code coverage driving additional paid smell, so additional users uh within our stage who are using paid features and finally, that pipeline tab back to the increase in usage for the stage monthly active users. So we anticipate that this will help drive that at least within our group, hopefully at the stage as well.

A

So things to pay attention to. I just wanted to call out that there are two issues in this milestone that changed: the user interface on the unit test report, the unit test history and the pipeline tab. So let's just make sure we coordinate on those team feel free to add more things to pay attention to, as you review the issues there and then planning tasks, I can now check off describe how the milestone aligns and it's back to you thanks folks.