TestEngineering/Services/SyncTestPlanV1
< TestEngineering | Services
Jump to navigation
Jump to search
Sync/Picl Test Plan V1
Intro/Summary/Notes
Intro
- TBD
Summary
- A complete snapshot of what it takes to test and release picl/sync: tools, processes, schedules, resources, etc
Notes
- This is a living document. As such, assume very regular changes, updates, and rewrites as we go through the Dev milestones of v1.
- This document is designed to accompany the v1 release. Although it will be used as a reference for the various Dev milestones for v1, it is not specific to any one milestone.
- Milestone-specific test plans could be broken out from here to focus on very specific test sections, as defined below.
- Requested sync-able collections for V1/M1:
- Awesomebar/History
- Passwords
- Open Tabs
- Bookmarks
- (supported per account, but not per device)
- Requested basic feature set for V1/M1:
- Device compatibility (desktop/mobile only, not FFox)
- Setup (Sign Up, Sign In)
- Account Management
- Password change/reset(forgot)
- Detach a device (maintain the account)
- Better security/encryption
- Performance/stability
Schedule
- TBD. Tracking here: https://wiki.mozilla.org/User_Services/Sync/v1
QA Team
- Services QA
- Edwin Wong - Manager
- James Bonacci - Sync/Picl Lead
- John Morrison
- Karl Thiessen
- Peter deHaan
- QA
- Various members of the Firefox Desktop and Mobile teams will be involved in the testing of V1.
- Note: Sync/Picl Teams information can be found here:
- QA head count (DRAFT)
- 1 FT automation/tools lead + QA team support
- 1 FT android client lead + QA team support
- 1 FT desktop client lead + QA team support
- 1 FT FFos lead + QA team support
- 1 FT Auth/Storage lead + QA team support
- 1 FT server/security/db lead + QA team support - TBD
- A subset of the FF and Services QA teams for testing when this goes to FF Nightly.
- The entire FF and Services QA teams as part of normal testing of FF Aurora, Beta, Release channels
- Challenges
- Recruiting QA and SoftVision (or other contractors) for testing Try builds
- Recruiting QA team for full testing during normal FF releases
- Recruiting community for testing Firefox channels when they become available (esp. if they have experience with Sync 1.x)
Email Lists and IRC
- Services QA: services-qa@mozilla.com
- QA Teams: qa@mozilla.com
- Sync and Picl: sync-dev@mozilla.org
- IRC: #picl
- #sync, #androidsync, #identity
Bug Reporting
- Dev-related issues will be mixed within Bugzilla and GitHub
- Product issues will all live in Bugzilla
- Mobile (Android) Tree/Meta: https://bugzilla.mozilla.org/showdependencytree.cgi?id=799726&hide_resolved=0
- Desktop Tree/Meta: https://bugzilla.mozilla.org/showdependencytree.cgi?id=905997&hide_resolved=0
- FFos Meta TBD
- User/QA/Testing bugs will live in Bugzilla, per mobile/desktop
- Classification: TBD
- Products: TBD
- Components: TBD
- Note: We may need to cross link Bugzilla bugs with GitHub issues
Main References
Wikis and Etherpads
- Main Site: https://wiki.mozilla.org/User_Services/Sync
- Milestone 1: https://etherpad.mozilla.org/SyncMilestone1
- Version 1: https://wiki.mozilla.org/User_Services/Sync/v1
- Goals: https://wiki.mozilla.org/User_Services/Sync/v1#Goals
- User Stories: https://wiki.mozilla.org/User_Services/Sync/v1#User_stories
- UX: https://wiki.mozilla.org/User_Services/Sync/v1#UX_design
- Migration: https://wiki.mozilla.org/User_Services/Sync/v1#Migration_strategy
- Technical Materials and Links: https://wiki.mozilla.org/User_Services/Sync#Technical_Materials
- Numerous other wikis and etherpads, including the following:
GitHub Repositories
- https://github.com/mozilla/mozilla-central
- https://github.com/mozilla/node-kvstore
- https://github.com/mozilla/node-srp/
- https://github.com/mozilla/jwcrypto
- https://github.com/mozilla/scrypt-helper
- https://github.com/mozilla/restmail.net
- https://github.com/mozilla/firefox-account-bridge
- https://github.com/mozilla/picl-gherkin