Fri, Oct 11
Thu, Oct 10
Do you think it would make sense to try to specify this session further in this direction?
Wed, Oct 9
Sure. Happy to do either.
Tue, Oct 8
We probably all know the "testing pyramid", but what we don't necessarily do is use the pyramid to guide our testing approaches or investments. I'm really interested in this topic and would like to see the concepts be more broadly applied.
I'm very interested in this topic. Over the past couple of years, I've been involved in a number of discussions on the topic, especially that of making beta cluster more "production-like". However, I don't think we've defined what "production-like" means. I'm of the belief that we may need to approach the question differently. Right now the discussions seem to be focused on a single production-like staging environment. Perhaps viewing it as several testing environments that have characteristics of the production would yield some alternatives that are more achievable. I think coupling that discussion with adiscussion about testing approaches would also be beneficial.
Happy to help with this session.
Depending on the amount of time we have for this session, I suggest that we limit it's scope to Code Review vs the broader Code Health topic. If we have enough time, I'd be happy to provide and overview of the other Code Health Group activities in play.
Sat, Sep 21
Thu, Sep 19
Sep 9 2019
Thanks @jbond. Appreciated.
Best practices from google:
Sep 6 2019
Sep 3 2019
Added Popups and Mobile Frontend extensions to pipeline.
Aug 19 2019
Aug 6 2019
Aug 5 2019
Jul 31 2019
Jul 29 2019
Jul 23 2019
We'll discuss at next CHM sync-up meeting.
Jul 19 2019
Jul 16 2019
Jul 11 2019
Jul 9 2019
@WDoranWMF, I do think this is a Code Health topic. I've added the Code-Health project tag to it so that it shows up on the Code Health Group's radar.
@WDoranWMF, I'll take ownership of this task for the time being.
Jun 28 2019
Jun 25 2019
Jun 18 2019
Jun 11 2019
I'll be moving this task to Done on the CS work board as RelEng is taking on CS responsabilities as it's being sunsetted.
Jun 6 2019
Do we have a sense of what is causing these rechecks? @zeljkofilipin, have any insight into this. I know we've discussed it a little in the past.
I am in favor of leaving them as voting, especially if the primary driver to changing that is their flaky nature. Although I do understand the issue at hand, I'd like to work to find a different solution to the problem of flaky tests. Monitoring and acting upon flaky tests hasn't been a priority in the past, but we are moving to bring more focus to that in the near future.
Jun 4 2019
Spoke with @Catrope and @MMiller_WMF re the ownership of this extension. We determined that this extension is outside the scope of the Growth team and would be better suited somewhere else. As such, this extension has returned to orphan status.
Hello @marcella, this extension came up as a Code Stewardship review request, but I've noticed that it is marked as being stewarded by the Editing team on developers/maintainers page. Just checking to see what the actual Code Stewardship status is before I dig any deeper.