Platform/2015-Q1-Goals: Difference between revisions
< Platform
Jump to navigation
Jump to search
(→A*Team: add highlights) |
(→QA) |
||
Line 34: | Line 34: | ||
=== QA === | === QA === | ||
See [[QA/Goals/2015q1|our wiki]] for the complete list | |||
''' Highlights:''' | |||
* {{ok|Automate kick off of update testing, automating entire release process save manual spot-checks}} | |||
* {{ok|Begin process for converting automated update and l10n tests to marionette in preparation for e10s (all P1 tests converted)}} | |||
* {{ok|Help relieve user headaches from Flash powered content}} | |||
* {{ok|Bring quality teams closer to engineering and increase technical acumen in high priority areas}} | |||
* {{ok|Create set of risk factor metrics to be used across codebase to identify potential areas of relative risk}} | |||
* {{ok|Make security testing automation more robust and more streamlined}} | |||
* {{ok|Complete payments automation coverage}} | |||
* {{ok|Create a community taskforce to do QA on a specific pilot project}} | |||
=== Web Engineering === | === Web Engineering === |
Revision as of 04:57, 14 January 2015
Platform
General Goals (by Team)
GFX
Layout
Media
DOM
JS
Accessibility
Perf
Networking
Mobile
A*Team
See our Trello board for the complete list.
Highlights:
- Support the conversion of mozmill Firefox update tests to Marionette
- MozReview: add autolander integration with Tryserver
- MozReview: improve Bugzilla integration
- Bugzilla: implement an alternate bug view
- Perfherder: develop a UI inside Treeherder that can be used to inspect Talos performance data
- Treeherder: create the ability to distinguish between Tier 1 and Tier 2 jobs
- Android: develop Android 4.4 emulator images that can be used for test jobs
- Prototype a "big data" project that logs detailed information about tests that can be used to normalize test chunks, identify tests that never fail versus those that do, and be of source of other metrics in the future
- Resolve issues that block us from releasing Marionette 1.0
QA
See our wiki for the complete list
Highlights:
- [ON TRACK] Automate kick off of update testing, automating entire release process save manual spot-checks
- [ON TRACK] Begin process for converting automated update and l10n tests to marionette in preparation for e10s (all P1 tests converted)
- [ON TRACK] Help relieve user headaches from Flash powered content
- [ON TRACK] Bring quality teams closer to engineering and increase technical acumen in high priority areas
- [ON TRACK] Create set of risk factor metrics to be used across codebase to identify potential areas of relative risk
- [ON TRACK] Make security testing automation more robust and more streamlined
- [ON TRACK] Complete payments automation coverage
- [ON TRACK] Create a community taskforce to do QA on a specific pilot project
Web Engineering
crash-stats
DXR
SUMO
- Finish BuddyUp Phase 1
- Finish Questions Forum redesign
- Contributor Metrics Dashboard
- Pay down Technical Debt
- Upgrade to the latest Django (1.7, most likely)
- Get SUMO on Python 2.7
- Switch to py.test
- Stop using test_utils
Input
- Upgrade to Django 1.7
- Upgrade other libraries to appropriate versions now that Input is on Python 2.7
- 12-factor app work (12 Factor App)
- Prepare for AWS move (set up a stage environment in AWS?)
- 1-5 gradient ratings (Gradient Sentiment)
- Thank you page overhaul (Thank you page) (via OPW intern)
Release Engineering / Release Operations / Developer Services
- Virtualize Windows builders and get builds running in the cloud
- Drive some of our builds out of taskcluster
- Schedule reduced test load (depends on A-team)
- Ship production quality 1.0 of MozReview and Autoland
- Scope and begin implementation of release automation changes with the goal to cut release time in half.
- Support OS X 10.10 builds with minimum additional cost
Security & Privacy
see Security Engineering 2015, Q1 Goals