Auto-tools/Projects: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
__NOTOC__
= Automation and Tools Projects =
{| style="width: 100%" class="fullwidth-table sortable"
Our projects can be broken up as follows:
|-
* Performance - Projects surrounding measurement of performance
| style="background:#efefef" width="25%" | '''Description'''
* Web Tools - Projects to build web tools and web UIs for automation frameworks
| style="background:#efefef" | '''Leader'''
* Automation - Projects to automate some process or create automation frameworks
| style="background:#efefef" | '''Goal'''
* Tool Infrastructure - Tool "building blocks" from which we can make other tools
| style="background:#efefef" | '''ETA'''
 
| style="background:#efefef" | '''Status'''
Please fill out this table with your best estimates for the projects you are involved in. An explanation of the fields:
* Area - one of the four project areas
* Project Name - the project name, and should be a wiki link to a project details page at Auto-tools/Projects/<projectname> (See Project Foo below for an example)
* Team Deps - Teams you will need to work with/depend on to drive this project
* Project Deps - Pieces of Tool infrastructure your project depends on
* Priority - the current priority of this project in terms of
* Size - Size of project in hours - include total here, put the breakdown on your details page
* Owner - The one (or rarely, two) people that own this project.
 
If you would like a sample details page to work from, feel free to use [[Feature_Page_Structure|the Firefox Feature Planning page for a template.]].
 
= The Projects =
 
{| class="fullwidth-table sortable" style="width: 950px"
|-
|-
| [[auto-tools/Projects/XTalos|Xperf + talos integration improvements]]
| style="font-weight: bold; background: #DDD; width: 100px" | Area
| jmaher
| style="font-weight: bold; background: #DDD; width: 100px" | Project
| complete xperf integration, migrate from time based collection, improve pageloader
| style="font-weight: bold; background: #DDD;" | Team Deps
| 2011 Q2-Q3
| style="font-weight: bold; background: #DDD;" | Project Deps
| style="font-weight: bold; background: #DDD; width: 50px" | Priority
| style="font-weight: bold; background: #DDD; width: 50px" | Size (hrs)
| style="font-weight: bold; background: #DDD; width: 150px" | Primary Owner
|-
|-
| [[auto-tools/Projects/MozBase|Mozharness Base Class Refactor]]
| Performance Measurements
| jgriffin + ahal + ted + ctalbert + jmaher
| User Responsiveness
| refactor test harnesses to use common modules and integrate easier with mozharness
| None
| 2011 Q2-Q3
| native events
| {{Pr1}}
| ??
| Ted
|-
|-
| [[Ateam/Winmo/1.0/todo| Android Automation]]
| Performance Measurements
| bmoss & jmaher & ctalbert
| [[Auto-tools/Projects/AddonStartupPerf|Addon Talos Testing]]
| Create full test integration for Android using the remote tests framework, support RelEng during roll out of that framework.
| AMO, Releng, IT
| 2011 Q1
| ??
| [[Ateam/Winmo/1.0/todo|LANDING]]
| {{Pr1}}
| ??
| Anode
|-
|-
| [[Auto-tools/Projects/Autolog| Autolog]]
| Performance Measurements
| jgriffin, jmaher, mcote
| [[Auto-tools/Projects/XTalos|Xperf Talos]]
| A tbpl-like test result system (both web UI and database) for viewing test results produced by various a-team projects, like mobile automation, crossweave, etc.
| Perf Team
| 2011 Q2
| .etl parser, results uploading
| TAKING OFF
| {{Pr2}}
| 30
| Jmaher
|-
|-
| [[auto-tools/Projects/ManifestDestiny| Universal Manifest Format for Tests]]
| Performance Measurements
| anode + jmaher
| Other Perf Measures
| Standardize manifest format for unit tests (+ talos?)
| Perf Team
| 2011 Q3ish
| Xperf talos
| IN FLIGHT
| {{Pr3}}
| 50
| Jmaher
|-
|-
| [[auto-tools/Projects/BugzillaReviewImprovement|Improving Bugzilla Review process]]
| Performance Measurements
| dkl
| [https://intranet.mozilla.org/Auto-tools/Projects/Eideticker Eideticker]
| Improve review experience in bugzilla by integrating splinter
| IT, cjones
| 2011 Q1-Q2
| native events, boards
| LANDING
| {{Pr2}}
| 60
| Ctalbert
|-
|-
| [[auto-tools/Projects/AddonStartupPerf|Measure AddOn startup performance]]
| Performance Measurements
| harth, anode
| [https://wiki.mozilla.org/Auto-tools/Projects/SpeedTests Speed Test Framework]
| Design and prototype a system for automating measuring addon startup performance.  Created system for automated talos testing of top 100 addons. Phase 2 for full testing of all addons is slated after this lands.]
| IT (for machine installations)
| 2011 Q1
| None (but might benefit from UX Platform)
| LANDING
| ??
| 40-64
| Mcote
|-
|-
| [[auto-tools/Projects/PurifyAutomation|Purify Integration]]
| Web Tools
| jgriffin
| Bugzilla REST API
| Integrate the new Purify machine into the larger Crash Automation and testing infrastructure
| ??
| 2010 Q2?
| ??
| WAITING FOR TAKEOFF (on IT)
| ??
| ??
| Dkl
|-
|-
| [[auto-tools/Projects/Loderunner|The Great Refactor (Loderunner)]]
| Web Tools
| all
| Bugzilla Pulse & Tool Integration
| Continual improvement step to refactor core common functionality into a set of shared components that can be used across the test harnesses. Beginning with manifests in mozmill and xpcshell as well as packaging httpd.js
| IT, Pulse
| 2011 Q1-Q2
|  
| IN FLIGHT
|  
| ??
| Glob
|-
|-
| [[auto-tools/Projects/WarOnOrange|The War on Orange]]
| Web Tools
| jgriffin, jmaher, jhammel, mcote, ctalbert, harth
| [https://wiki.mozilla.org/BMO/Updated_Guided_Bug_Entry Updated Guided Bug Entry]
| Web dashboard for tracking intermittent oranges in our unittests.
|  
| 2010 Q4
|
| LANDED
| {{Pr2}}
| 30
| Glob
|-
|-
| [[auto-tools/Projects/BugStats|BugStats Websites]]
| Web Tools
| mcote
| [https://wiki.mozilla.org/BMO/InstantSearch "Instant" Quick Search]
| Web dashboards for viewing statistics from Bugzilla--blockers, nominations, reviews, bugs recently closed, etc.
| IT, Metrics
| 2011 Q1
|
| TAKING OFF
| {{Pr3}}
| Unknown
| Glob
|-
|-
| [[auto-tools/Projects/FennecPT|Fennec Profile Tool]]
| Web Tools
| mcote
| HG Improvements
| GUI tool for downloading & swapping Fennec profiles.
| ??
| 2011 Q1
| ??
| TOUCH AND GO
| ??
| ??
| (contractor)
|-
|-
| [[auto-tools/Projects/SpeedTests|SpeedTests]]
| Web Tools
| mcote
| TCM (Litmus 2)
| Suite of automated JavaScript-based graphics speed tests.
| ??
| 2011 Q1
| ??
| TAKING OFF
| ??
|}
| ??
 
| (contractor)
= Proposed Projects =
* Our own [[auto-tools/Goals/BigDreams|Big Ideas]]
* Integrate CoScriptor natural language with Mozmill
* Weave Thick Client Automation
* [[auto-tools/Projects/WikiZilla|Wiki <-> Bugzilla Integration]]
 
= Completed Projects =
{| style="width: 100%" class="fullwidth-table sortable"
|-
|-
| style="background:#efefef" width="25%" | '''Description'''
| Web Tools
| style="background:#efefef" | '''Leader'''
| [https://wiki.mozilla.org/Auto-tools/Projects/Autolog AutoLog]
| style="background:#efefef" | '''Goal'''
| None
| style="background:#efefef" | '''Landed'''
| UX Platform
| {{Pr1}}
| 240
| Jgriffin
|-
|-
| Crash and Valgrind test Automation system
| Web Tools
| ?
| [https://wiki.mozilla.org/Auto-tools/Projects/WarOnOrange WOO]
| ?
| Metrics
| ?
| UX Platform
| {{Pr1}}
| 120
| Jgriffin
|-
|-
| Mozmill 1.4
| Web Tools
| ?
| Bug Hunter UI
| ?
| ??
| ?
| UX Platform
| ??
| ??
| Bc/Mcote
|-
|-
| Remote (aka Mobile) Test Refactoring for Mochitest and Reftest and XPCShell
| Web Tools
| ?
| [[Auto-tools/Projects/BugStats|Bug Stats Websites]]
| ?
| RelDrivers
| ?
| UX Platform
| {{Pr3}}
| 0
| Mcote
|-
|-
| Crash/Valgrind Automation UI 1.0
| Automation
| ?
| Bug Hunter Framework
| ?
| IT
| ?
| spider, sisyphus
| ??
| ??
| Bc
|-
|-
| QA Companion tool
| Automation
| ?
| Mozmill 2.0
| ?
| RelEng
| ?
| native events
| ??
| ??
| Ctalbert
|-
|-
| OOPP test infrastructure and NPAPI test creation
| Automation
| ?
| [https://wiki.mozilla.org/Services/Sync/FxSync/Crossweave2 Crossweave 2]
| ?
| Services
| ?
| Mozmill (mozprofile, mozrunner)
| {{Pr2}}
| 160
| Jgriffin
|-
|-
| JS Reftest test suite
| Automation
| ?
| [[Ateam/Projects/Uber-crawl|Uber-crawl]]
| ?
| IT, JS, Metrics, Layout
| ?
| spider, sisyphus
| ??
| ??
| Bc
|-
|-
| [[auto-tools/Projects/MozmillBuildbot| Integrate Mozmill into Buildbot]]
| Automation
| jhammel
| Harnesses that need Servers
| Integrate Mozmill test harness into Buildbot automation system
| RelEng, F1, Sync, Firebug, Safe Browsing, Identity, Security, Apps
| 2010 Q3
| Mozharness, Autolog
| ??
| ??
| ??
|-
|-
| [[auto-tools/Projects/Halreftest|Grafx Bot]]
| Tool Infrastructure
| jgriffin
| [[Auto-tools/Projects/ManifestDestiny|Manifest Destiny (landing for xpcshell?)]]
| Create a crowd-source extension for graphics subsystem testing
| N/A
| 2010 Q2
| N/A
| {{Pr2}}
| 20
| Jhammel/Jmaher
|-
|-
| [[auto-tools/Projects/CrashAutoUIv2|Crash & Valgrind Automation UI v2]]
| Tool Infrastructure
| harth & bc
| [[Auto-tools/Projects/HTTP_Record_Replay|HTTP Record/Replay]]
| Create a UI that aids in correlation of crash and test data to help diagnose problems in the product.
| ??
| 2010 Q2ish
| ??
| ??
| ??
| ??
|-
|-
| [[auto-tools/Projects/CrossWeave|CrossWeave]]
| Tool Infrastructure
| jgriffin
| Native Events
| A new automated test framework for testing client/server interactions in Weave, using a Firefox extension
| ??
| 2010 Q2
| ??
| ??
| ??
| Ahal
|-
|-
| [[auto-tools/Projects/Mozmill1.5|Mozmill 1.5]]
| Tool Infrastructure
| ctalbert, harth, ahal, jhammel
| [[Auto-tools/Projects/MozBase|MozBase]]
| Fixes and a UI refresh plus new logging backend for Mozmill
| RelEng
| 2010 Q2-Q3
| Mozmill (mozprocess, mozprofile, logging), automation.py
| {{Pr2}}
| 160
| Jmaher
|-
|-
| [[auto-tools/Projects/CrashAutomationRollout|Crash Automation Rollout]]
| Tool Infrastructure
| bc
| [[Auto-tools/Projects/WebUXPlatform|Web UX Platform]]
| Work with IT to roll out the crash & valgrind automation system to a set of production machines in the colo
| IT
| 2010 Q2
| None, but benefits from existing web projects
| ??
| 80-120
| Mcote
|-
|-
| [[auto-tools/Projects/ProfileManager|Profile Manager Replacement]]
| Tool Infrastructure
| jgriffin + jhammel
| [[Auto-tools/Projects/SpecialPowers_Migration|SpecialPowers]]
| The profile manager is going away, we will need to build a better tool for a replacement.
| Developers
| 2010 Q2-Q3
| Most test harnesses
| {{Pr1}}
| ??
| Ted
|}
|}


= Legend =
= Proposed =
Using the airplane metaphors that the Firefox team started with.  Let me know if you have a better suggestion.
* (BLANK) - Not started
* WAITING FOR TAKEOFF - Project blocked by an external dependency
* TAKING OFF - Beginning design process, early work
* IN FLIGHT - In active development
* TOUCH AND GO - Find/fix mode.  In early testing. (This refers to practice landings that pilots do)
* LANDED - Done


= Template =
= \o/ Completed \o/ =
We might change this in the future, but to get started we can use the [https://wiki.mozilla.org/Firefox/Projects/Template Firefox Project Template] if it helps create pages for these projects.
* <strike>JS Reftest suite</strike>
* <strike>Mozmill 1.4</strike>
* <strike>QA Companion Tool </strike>
* <strike>OOPP test infrastructure and NPAPI test suite creation </strike>
* <strike>[https://wiki.mozilla.org/Auto-tools/Projects/Halreftest GrafxBot</strike>
* <strike>[https://wiki.mozilla.org/Auto-tools/Projects/CrossWeave Crossweave v1</strike>
* <strike>Mozmill 1.5</strike>
* <strike>Android Mochitest, Reftest, Js Reftest, Crashtest, Talos</strike>
* <strike>Bug Hunter Initial Rollout</strike>
* <strike>[https://wiki.mozilla.org/Auto-tools/Projects/FennecPT Fennec Profile Manager]</strike>
* <strike>[https://wiki.mozilla.org/Auto-tools/Projects/ProfileManager Desktop Profile Manager Replacement]</strike>
* <strike>SpeedTest v1 Framework</strike>
* <strike>[http://brasstacks.mozilla.com/toolbox Toolbox]</strike>

Revision as of 23:08, 15 June 2011

Automation and Tools Projects

Our projects can be broken up as follows:

  • Performance - Projects surrounding measurement of performance
  • Web Tools - Projects to build web tools and web UIs for automation frameworks
  • Automation - Projects to automate some process or create automation frameworks
  • Tool Infrastructure - Tool "building blocks" from which we can make other tools

Please fill out this table with your best estimates for the projects you are involved in. An explanation of the fields:

  • Area - one of the four project areas
  • Project Name - the project name, and should be a wiki link to a project details page at Auto-tools/Projects/<projectname> (See Project Foo below for an example)
  • Team Deps - Teams you will need to work with/depend on to drive this project
  • Project Deps - Pieces of Tool infrastructure your project depends on
  • Priority - the current priority of this project in terms of
  • Size - Size of project in hours - include total here, put the breakdown on your details page
  • Owner - The one (or rarely, two) people that own this project.

If you would like a sample details page to work from, feel free to use the Firefox Feature Planning page for a template..

The Projects

Area Project Team Deps Project Deps Priority Size (hrs) Primary Owner
Performance Measurements User Responsiveness None native events P1 ?? Ted
Performance Measurements Addon Talos Testing AMO, Releng, IT ?? P1 ?? Anode
Performance Measurements Xperf Talos Perf Team .etl parser, results uploading P2 30 Jmaher
Performance Measurements Other Perf Measures Perf Team Xperf talos P3 50 Jmaher
Performance Measurements Eideticker IT, cjones native events, boards P2 60 Ctalbert
Performance Measurements Speed Test Framework IT (for machine installations) None (but might benefit from UX Platform) ?? 40-64 Mcote
Web Tools Bugzilla REST API ?? ?? ?? ?? Dkl
Web Tools Bugzilla Pulse & Tool Integration IT, Pulse ?? Glob
Web Tools Updated Guided Bug Entry P2 30 Glob
Web Tools "Instant" Quick Search IT, Metrics P3 Unknown Glob
Web Tools HG Improvements ?? ?? ?? ?? (contractor)
Web Tools TCM (Litmus 2) ?? ?? ?? ?? (contractor)
Web Tools AutoLog None UX Platform P1 240 Jgriffin
Web Tools WOO Metrics UX Platform P1 120 Jgriffin
Web Tools Bug Hunter UI ?? UX Platform ?? ?? Bc/Mcote
Web Tools Bug Stats Websites RelDrivers UX Platform P3 0 Mcote
Automation Bug Hunter Framework IT spider, sisyphus ?? ?? Bc
Automation Mozmill 2.0 RelEng native events ?? ?? Ctalbert
Automation Crossweave 2 Services Mozmill (mozprofile, mozrunner) P2 160 Jgriffin
Automation Uber-crawl IT, JS, Metrics, Layout spider, sisyphus ?? ?? Bc
Automation Harnesses that need Servers RelEng, F1, Sync, Firebug, Safe Browsing, Identity, Security, Apps Mozharness, Autolog ?? ?? ??
Tool Infrastructure Manifest Destiny (landing for xpcshell?) N/A N/A P2 20 Jhammel/Jmaher
Tool Infrastructure HTTP Record/Replay ?? ?? ?? ?? ??
Tool Infrastructure Native Events ?? ?? ?? ?? Ahal
Tool Infrastructure MozBase RelEng Mozmill (mozprocess, mozprofile, logging), automation.py P2 160 Jmaher
Tool Infrastructure Web UX Platform IT None, but benefits from existing web projects ?? 80-120 Mcote
Tool Infrastructure SpecialPowers Developers Most test harnesses P1 ?? Ted

Proposed

\o/ Completed \o/

Retrieved from "https://wiki.mozilla.org/index.php?title=Auto-tools/Projects&oldid=319669"