# mozreview Published articles for mozreview. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Outreachy Internship Update: Learning Mozilla's Development Process and Refactoring Marionette's Python Test Runner DevFeed: [Outreachy Internship Update: Learning Mozilla's Development Process and Refactoring Marionette's Python Test Runner]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-08-02T00:00:00Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Development](), [Mozilla](), [Testing](), [Python](), [Refactoring](), [Test-driven development](), [Pytest](), [Firefox]() Tags: [development-process](), [firefox](), [internship](), [marionette](), [mozilla](), [mozreview](), [outreachy](), [pytest](), [python](), [refactoring](), [test](), [testing](), [treeherder]() ### AI overview An Outreachy intern reflects on the first part of an internship with Mozilla, describing the process of learning Mozilla's development tools and workflows. The article also outlines work on test-driven refactoring of Marionette's Python test runner and previews a follow-up post about its test runner and harness. ### Source excerpt It feels like yesterday that I started my Outreachy internship, but it was actually over 2 months ago! For the last couple of weeks I've been on Outreachy hiatus because of EuroPython, moving from Saarbrücken to Berlin, and my mentor being on vacation. Now I'm back, with 6 weeks left in my internship! So it seems like a good moment to check in and reflect on how things have been going so far, and what's in store for the rest of my time as an Outreachyee. What have I been up to? Learning how to do the work In the rather involved application process for Outreachy, I already had to spend quite a bit of time figuring out the process for making even the tiniest contribution to the Mozilla codebase. But obviously one can't learn everything there is to know about a project within a couple of weeks, so a good chunk of my Outreachy time so far was spent on getting better acquainted with: The tools I've already written about my learning experiences with Mercurial, but there were a lot of other components of the Mozilla development process that I had to learn about (and am still learning about), such as Bugzilla, MozReview, Treeherder, Try, Mach... Then, since the project I'm working focuses on testing, I had to grok things like Pytest and Mock. Since most everything I'm doing is in Python, I've also been picking up useful Python tidbits here and there. The project My internship project, "Test-driven refactoring of Marionette's Python test runner", relates to a component of the Marionette project, which encompasses a lot of moving parts. Even figuring out what Marionette is, what components it comprises, how these interrelate, and which of them I need to know about, was a non-trivial task. That's why I'm writing a couple of posts about the project itself - one down, one to go - to crystallize what I've learned and hopefully make it a little easier for other people to get through the what-even-is-it steps that I've been going through. This post is a sort of "intermission", so sta ## adding "reviewer delegation" to MozReview DevFeed: [adding "reviewer delegation" to MozReview]() Original publisher: [Read original article]() Author: glob Published: 2016-07-04T07:20:06Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Code review](), [Extension](), [Authorization](), [Mozilla](), [Git]() Tags: [code-review](), [extension](), [mozilla](), [mozreview](), [permission](), [review]() ### AI overview This technical article describes the design challenges behind adding reviewer delegation to MozReview. It explains how MozReview integrates Review Board, Bugzilla, Mercurial, Git, and automation, and discusses permission handling, draft updates, and preserving the identity of the authenticated user when changes are attributed to the submitter. ### Source excerpt Background One of the first projects I worked on when I moved to the MozReview team was "review delegation". The goal was to add the ability for a reviewer to redirect a review request to someone else. It turned out to be a change that was much more complicated than expected. MozReview is a Mozilla [...] ## mozreview and inline comments on the diff view DevFeed: [mozreview and inline comments on the diff view]() Original publisher: [Read original article]() Author: glob Published: 2016-03-23T15:39:21Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Code review](), [User interface design](), [HTML]() Tags: [code-review](), [design](), [development](), [html](), [interface](), [mozreview](), [review]() ### AI overview The article discusses plans to change MozReview and Review Board so review comments appear as inline blocks on the diff instead of small squares in the left column. The team created a design document, began an HTML mockup, and started discussions with the upstream Review Board development team, but upstream acceptance remained uncertain. ### Source excerpt when a comment is left on a review in review board/mozreview it is currently displayed as a small square in the left column. our top reviewers have strongly indicated that this is suboptimal and would prefer to match what most other code review systems do in displaying comments as an inline block on the diff. [...] ## moving from bugzilla to mozreview DevFeed: [moving from bugzilla to mozreview]() Original publisher: [Read original article]() Author: glob Published: 2015-10-22T19:53:11Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Mozilla](), [Extension](), [Authentication](), [client](), [servers](), [Bot]() Tags: [authentication](), [bots](), [extension](), [mozilla](), [mozreview](), [server]() ### AI overview The author describes moving full time from Bugzilla to MozReview and outlines MozReview's architecture and dependencies. MozReview extends Review Board, uses Bugzilla for authentication, relies on LDAP for commit-level checks, and includes client and server Mercurial extensions; automated pushes to Try and Mozilla-central, along with planned static analysis bots, are also mentioned. ### Source excerpt for the next couple of quarters (at least) i'll be shifting my attention full time from bugzilla to mozreview. this switch involves a change of language, frameworks, and of course teams. i'm looking forward to new challenges. one of the first things i've done is sketch out a high level architectural diagram of mozreview and [...] ## Bugzilla and MozReview changes pushed, including group management, reviewer suggestions, bug history, and MFA password updates DevFeed: [Bugzilla and MozReview changes pushed, including group management, reviewer suggestions, bug history, and MFA password updates]() Original publisher: [Read original article]() Author: glob Published: 2015-10-06T07:28:46Z Content type: release Language: en Sources: [Mozilla Automation]() Topics: [bug](), [Mozilla](), [Support](), [MFA](), [passwords]() Tags: [automatic](), [bmo](), [bug](), [display](), [history](), [mfa](), [mozilla](), [mozreview](), [password](), [patches](), [regression](), [reports](), [support](), [tools](), [user-stories]() ### AI overview A push to bugzilla.mozilla.org introduced changes to bug management, reviewer suggestions, group membership reports, inactive-user removal, MozReview requests, bookmarkable user-story templates, bug history navigation, commit and data display, regression dependencies, patch warnings, and password changes with MFA enabled. ### Source excerpt the following changes have been pushed to bugzilla.mozilla.org: [1209332] Make the master kick-off bug "Confidential Mozilla Employee Bug" by default [1209971] Suggested reviewers should exclude the current user from the list displayed [1200958] group owners should always be able to view group membership reports for their groups [1196620] support automatic removal of inactive users from [...]