canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,776
edits
Features/Firefox/Easy UI Feature Testing: Difference between revisions
Features/Firefox/Easy UI Feature Testing (view source)
Revision as of 23:41, 2 March 2012
, 2 March 2012no edit summary
Gregg.lind (talk | contribs) (Created page with "{{FeatureStatus |Feature name=Easy UI Feature Testing (integrate TestPilot like features) |Feature stage=Draft |Feature status=In progress |Feature version=Firefox 12 |Feature he...") |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=Easy UI Feature Testing (integrate TestPilot like features) | |Feature name=Easy UI Feature Testing and "Success Evaluation" (integrate TestPilot like features) | ||
|Feature stage=Draft | |Feature stage=Draft | ||
|Feature status=In progress | |Feature status=In progress | ||
|Feature version=Firefox | |Feature version=Firefox 13 | ||
|Feature health=OK | |Feature health=OK | ||
}} | }} | ||
| Line 13: | Line 13: | ||
Collecting data has Privacy implications | Collecting data has Privacy implications | ||
Publishing collected data has Privacy Implications | Publishing collected data has Privacy Implications | ||
|Feature overview=By incorporating Test-Pilot-like features into Firefox, it makes it easier for Feature Developers to design, implement, and instrument | What makes a "successful" feature? | ||
|Feature overview=Right now, features can go into FX without knowing if they will be 'successful' or not. What 'success' even means is a bit nebulous! | |||
By incorporating Test-Pilot-like features into Firefox, it makes it easier for Feature Developers to design, implement, and instrument new features. | |||
With usual statistics (among targeted test populations), product managers can make better decisions around which features should go forward, be revised, or be removed. This removes one of the barriers to having every feature in Firefox go through usability testing. | |||
|Feature users and use cases=* A/B testing of user features | |Feature users and use cases=* A/B testing of user features | ||
* UI experiments | * UI experiments | ||
* all new user features | * all new user features | ||
|Feature dependencies=bringing TP like code (with mechanisms for watching events, deploying modified UI elements) into main build. | |||
|Feature functional spec=Include TP like functionality into FX directly, making the addon superfluous, on all FX platforms. | |||
Specific functionalities: | |||
* record/report any event on any id-able element, with timestamp, for a user. | |||
* choose to run a study / instrumentation on a particular subset of users | |||
* deploy variations in UI (via restartless addon, or another mechanism) | |||
|Feature ux design=Users should be able to see submitted data, similar to current TP implementation. | |||
Users get notification of initial opt-in | |||
Users can destroy / opt-out / not submit their data. | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||
|Feature priority=Unprioritized | |Feature priority=Unprioritized | ||
}} | }} | ||
{{FeatureTeamStatus}} | {{FeatureTeamStatus | ||
|Feature security status=sec-review-needed | |||
|Feature security notes=Please schedule with curtisk | |||
}} | |||