Litmus:Extension: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(25 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= Initial Mockups =
= Overview =
See some screencaps at [http://zachlipton.com/qaExtensionMockups]
 
The QA Community extension is meant to be an easy way to get community members involved in the QA process. It pulls testcases from Litmus and provides an response form, all within the extension interface. The extension also includes notifications for important QA events such as Bug Days, and keeps users up-to-date with live feeds from the QMO site and forums. Chatzilla is also bundled in with the extension, with one-click access to the #qa channel.


= Goals =  
= Goals =  
Line 10: Line 11:


= Feature Areas =  
= Feature Areas =  
* Initial setup
 
** Helps users get setup with an account if they don't already have a Litmus account. Provides an introduction to Mozilla QA, what we do, how testing works.
* General QMO tab -- updates on news, forums, etc.
** One guided process from installing the extension to submitting their first test result, real easy and welcoming
* Litmus tab -- the heart of the extension. Allows users to get testcases and submit results from within the extension. A setup wizard detects most system settings and helps new users set up a Litmus account.
* Running tests
* Chatzilla tab -- one click launches the user into the wacky world of the #qa channel!
** Select a testing area. Mozilla QA can push recommended areas to users to test around new code/features.
* Settings/Help, for the confused or misconfigured.
** Run a test, select a result, next test is shown
 
** Positive feedback to users: you've run this many tests, top testers of the week, etc...
= Current Status =
* Community aspects
 
** Joga-style notification of special testing events, linking directly to the relevant set of tests and IRC
Currently, we're circulating the extension among the qa team internally. We hope to push to a small group of community testers and eventually the larger QA community soon.  
** Links to QMO resources that encourage people to get involved in other QA areas: bug days, bugzilla triage, etc...
 
We need:
 
* Content writers. All of the content is pulled live from the QMO site, so all you have to do is edit or create some wiki pages.
* More testing. We have some early results coming in from the QA team, but most of the testing has been done ourselves, and we don't have great coverage so far. Also, comments on UI/UX would be great.
 
Screenshots:
[http://people.mozilla.com/~bhsieh/litmusscreenshot.jpg 1],
[http://people.mozilla.com/~bhsieh/litmusscreenshot2.jpg 2]


= Other ideas =
= Other ideas =
* Direct link into IRC to bring testers into #qa/#testday
* David Hamp, a student at Seneca, was working on a Litmus extension but apparently didn't have much time to devote to the project during the past school year. Zach emailed him to determine what he's done and whether he's interested in working more on this. Reply: seems like he's extremely busy right now, but  interested in the long-term.
* Branch/build detection to encourage testers to use current builds and to test RCs before releases. Target tests and messages to branch and trunk users.
* Need standard Big Warnings about using development software. Automatic profile backup? Need docs on how to manage having multiple versions installed and such.
* Need standard Big Warnings about using development software. Automatic profile backup? Need docs on how to manage having multiple versions installed and such.
* Possible rewards system to encourage our testers. Maybe display lifetime/monthly/session number of test results submitted, with prizes for the winners! Or something.
* Other tabs/buttons to hook into QMO
* Other tabs/buttons to hook into QMO


Line 31: Line 38:
* QMO Extension? Integrate the QMO branding
* QMO Extension? Integrate the QMO branding
* Tie this in with the Mozilla beta program concept somehow?
* Tie this in with the Mozilla beta program concept somehow?
* Hermes - Notification server
* Need a Greek name for the extension ;-)


= Questions =  
=Installing the extension=
* How to implement IRC? Options are to bundle Chatzilla (around 300kb, MPL licensed), or to go with some kind of Java solution.
The extension can be installed by browsing to: [http://landfill.bugzilla.org/mozillaQA/latest.xpi http://landfill.bugzilla.org/mozillaQA/latest.xpi]
(you'll need to click the link in the popup to allow 
landfill.bugzilla.org to install extensions)
It works on the 2.0 branch and on the trunk. Just click the QMO logo 
in the browser's status bar to get started once you install.


= Outstanding tasks of interest =
(Note: We're still working out the bugs in this extension. Hopefully this will be ready for the prime time soon, but until then, download at your own risk!)
* Rewrite account setup/creation code securely (without wrappedjsobject)


= Content pulled from external urls =
= Content pulled from external urls =
* QMO
* QMO
** Upcoming Events feed - [http://quality.mozilla.org/event/2007/06/21/feed/all/all/ the event feed]
** Upcoming Events feed - [http://quality.mozilla.org/event/2007/06/21/feed/all/all/ the event feed]
*** Jay created a new feed at http://quality.mozilla.org/extension/upcomingevents_feed and will update the code
** Recent forum posts feed - Pulled from an [http://quality.mozilla.org/extension/forum_topics rss feed] generated from a [http://quality.mozilla.org/admin/build/views/edit/9 custom view] that pulls the 10 most recent forum topics by creation date
** Recent forum posts feed - Pulled from an [http://quality.mozilla.org/extension/forum_topics rss feed] generated from a [http://quality.mozilla.org/admin/build/views/edit/9 custom view] that pulls the 10 most recent forum topics by creation date
** The latest from QMO - Generated from the top post in the [http://quality.mozilla.org/rss.xml main RSS feed]
** The latest from QMO - Generated from the top post in the [http://quality.mozilla.org/rss.xml main RSS feed]
Line 46: Line 59:
* Bugzilla
* Bugzilla
** Currently, the Bugzilla tab displays an [http://quality.mozilla.org/extension/bugzillatab_feed rss feed] that is automatically generated from [http://quality.mozilla.org/extension/bugzillatab this QMO page]
** Currently, the Bugzilla tab displays an [http://quality.mozilla.org/extension/bugzillatab_feed rss feed] that is automatically generated from [http://quality.mozilla.org/extension/bugzillatab this QMO page]
** UPDATE: For now, no live Bugzilla content.
* Litmus
* Litmus
** extension.cgi and json.cgi (parts of which are in zach's extension tree)
** extension.cgi and json.cgi (now landed in CVS)
* Notifications
** Served by Hermes, accessed through http://litmus.mozilla.org/hermes/1/ (currently just a static xml document). The key directory on the litmus server is /opt/webtools/hermes
 
= Current Contributors =
*Jay Patel -- project lead, ui development, qmo content
*Clint Talbert -- bug fixing, feature development
*Zach Lipton -- initial work, layout, notifications, prefs. Project member with CVS access.
*Ben Hsieh -- Litmus tab, some layout improvements.
*Zach Linder -- CSS, general theming.
 
= Key Links =
* See the project [http://www.zachlipton.com/extensionStatus/ Status Page] (perpetually out of date)
* [[Litmus:Extension/Notification|Notification system design]]

Latest revision as of 19:00, 10 March 2008

Overview

The QA Community extension is meant to be an easy way to get community members involved in the QA process. It pulls testcases from Litmus and provides an response form, all within the extension interface. The extension also includes notifications for important QA events such as Bug Days, and keeps users up-to-date with live feeds from the QMO site and forums. Chatzilla is also bundled in with the extension, with one-click access to the #qa channel.

Goals

  • Make it easier for new testers to get started
  • Allow testers to view tests and submit results from a separate window inside the app
  • Make testers feel valued and encourage them to keep testing
  • Help integrate testers into the community
  • Encourage participation in special events (testdays, pre-release testing, etc...)

Feature Areas

  • General QMO tab -- updates on news, forums, etc.
  • Litmus tab -- the heart of the extension. Allows users to get testcases and submit results from within the extension. A setup wizard detects most system settings and helps new users set up a Litmus account.
  • Chatzilla tab -- one click launches the user into the wacky world of the #qa channel!
  • Settings/Help, for the confused or misconfigured.

Current Status

Currently, we're circulating the extension among the qa team internally. We hope to push to a small group of community testers and eventually the larger QA community soon.

We need:

  • Content writers. All of the content is pulled live from the QMO site, so all you have to do is edit or create some wiki pages.
  • More testing. We have some early results coming in from the QA team, but most of the testing has been done ourselves, and we don't have great coverage so far. Also, comments on UI/UX would be great.

Screenshots: 1, 2

Other ideas

  • Need standard Big Warnings about using development software. Automatic profile backup? Need docs on how to manage having multiple versions installed and such.
  • Possible rewards system to encourage our testers. Maybe display lifetime/monthly/session number of test results submitted, with prizes for the winners! Or something.
  • Other tabs/buttons to hook into QMO

Naming

  • QMO Extension? Integrate the QMO branding
  • Tie this in with the Mozilla beta program concept somehow?
  • Hermes - Notification server
  • Need a Greek name for the extension ;-)

Installing the extension

The extension can be installed by browsing to: http://landfill.bugzilla.org/mozillaQA/latest.xpi (you'll need to click the link in the popup to allow landfill.bugzilla.org to install extensions) It works on the 2.0 branch and on the trunk. Just click the QMO logo in the browser's status bar to get started once you install.

(Note: We're still working out the bugs in this extension. Hopefully this will be ready for the prime time soon, but until then, download at your own risk!)

Content pulled from external urls

Current Contributors

  • Jay Patel -- project lead, ui development, qmo content
  • Clint Talbert -- bug fixing, feature development
  • Zach Lipton -- initial work, layout, notifications, prefs. Project member with CVS access.
  • Ben Hsieh -- Litmus tab, some layout improvements.
  • Zach Linder -- CSS, general theming.

Key Links

Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Litmus:Extension&oldid=86079"