Closed Bug 1428876 (testing-product-reorg) Opened 6 years ago Closed 6 years ago

Re-organize the Testing product

Categories

(bugzilla.mozilla.org :: Administration, enhancement, P3)

Production
enhancement

Tracking

()

RESOLVED FIXED

People

(Reporter: ahal, Assigned: emceeaich)

References

(Blocks 1 open bug)

Details

(Whiteboard: [bmo-workday-2018-01-27])

User Story

Move these components to the 'Testing Graveyard' product:
external-media-tests
Fennec Profile Tool
JSMarionette
Minotaur
Orangutan
Peptest
ProfileManager
Sisyphus
SutAgent
Test Informant
webQA

Merge these components with Testing::Mochitest:
BrowserTest
Mochitest Chrome

Merge these components with Testing::General
httpd.js
New Frameworks
ssltunnel

Create these new components:
CPPUnitTest -  Please file bugs here for issues with the
               cppunittest framework. For test related
               issues, file against the component under
               test.
GTest -        Please file bugs here for issues with the
               GTest harness. For test related issues,
               file against the component under test.
Mozbase Rust - A collection of Rust crates for managing
               common test related operations.
Python Test -  Please file bugs here for issues with the
               python unittest framework, including mach
               command and pytest integrations. For test
               related issues, file against the component
               under test.
Note to bz admins:
The desired list of components is TBD, so there is nothing to do here yet.

The Testing product on bugzilla is woefully out of date. I count ~13 components that could likely be moved to the graveyard without complaint. Another ~5 are pretty small and could likely be merged with related components. Meanwhile there are many projects which warrant their own component but don't yet have one.

Here is my initial proposal for the existing components:
ActiveData -> Data Platform and Tools::ActiveData (?)
Autophone
AWFY
AWSY
BrowserTest -> Testing::Mochitest
Code Coverage
external-media-tests -> Graveyard
Fennec Profile Tool -> Graveyard
Firefox UI Tests
geckodriver
General
httpd.js -> Testing::General
JSMarionette -> Graveyard
Lint -> Firefox Build System and Automation::Lint (might happen in bug 1406536)
Marionette
Minotaur -> Graveyard
Mochitest
Mochitest Chrome -> Testing::Mochitest
Mozbase
mozregression
mozscreenshots
New Frameworks -> Testing::General
Orangutan -> Graveyard
Peptests -> Graveyard
Profile Manager -> Graveyard
Reftest
Sisyphus
ssltunnel -> Testing::General
SutAgent -> Graveyard
Talos
Test Informant -> Graveyard
TPS -> Graveyard
webQA -> Graveyard
web-platform-tests
XPCShell Harness

I'll put this into an etherpad and solicit feedback on the mailing lists before going any further.
Here's an etherpad with the same proposal:
https://public.etherpad-mozilla.org/p/PFmWKPFfZw

Feel free to modify it and/or add new component proposals to the bottom.
Here's data on the number of open bugs, plus the most recently modified bug for each component in the Testing product:
https://gist.github.com/ahal/792eae6fafb557a6955d3fd9cf93d94e#file-testing-components-md

This data was derived from the jupyter notebook found in the same gist, it should help make the decision to move components around a little easier.
(In reply to Andrew Halberstadt [:ahal] from comment #0)
> TPS -> Graveyard

TPS is still in use. Mark do you know who currently owns this harness? Is it still you?
Flags: needinfo?(markh)
Blocks: 1372059
I'll leave TPS off the list for now.
Flags: needinfo?(markh)
(In reply to Henrik Skupin (:whimboo) from comment #3)
> (In reply to Andrew Halberstadt [:ahal] from comment #0)
> > TPS -> Graveyard
> 
> TPS is still in use. Mark do you know who currently owns this harness? Is it
> still you?

Sorry for the delay - I was on PTO. FYI, it is still owned by the Sync team and still seeing active development and use.
Please also move Testing:Sisyphus into Graveyard
User Story: (updated)
Hey Emma and Dylan. I've update the user story with the specific actions that should be taken here. Let me know if you'd prefer I file separate bugs so the breakdown of work is more manageable.

Otherwise, let me know if you need any other information from me. Thanks!
User Story: (updated)
Flags: needinfo?(ehumphries)
Flags: needinfo?(dylan)
Flags: needinfo?(ehumphries)
Priority: -- → P3
Whiteboard: [bmo-workday-2018-01-27]
This part is done:

Move these components to the 'Testing Graveyard' product:
external-media-tests
Fennec Profile Tool
JSMarionette
Minotaur
Orangutan
Peptest
Profile Manager
Sisyphus
SutAgent
Test Informant
webQA
Assignee: ehumphries → dylan
Flags: needinfo?(dylan)
This part is done:

Merge these components with Testing::Mochitest:
BrowserTest
Mochitest Chrome
This part is done.

Merge these components with Testing::General
httpd.js
New Frameworks
ssltunnel
Assignee: dylan → ehumphries
Created these new components in Testing

CPPUnitTest
GTest
Mozbase Rust
Python Test

These need triage leads, I've set :ahal for now. Please let me know if that should be different.
Flags: needinfo?(ahalberstadt)
Hey Emma, please set the triage owner for Mozbase Rust to jgraham@mozilla.com.

You can leave the other 3 as me for now, thanks!
Flags: needinfo?(ahalberstadt)
Done!
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Blocks: 1433974
I still see testing::Sisyphus available, :dylan can you double check that?
Flags: needinfo?(dylan)
I'll need to put this into the calendar.
Flags: needinfo?(dylan)
You need to log in before you can comment on or make changes to this bug.