Litmus:Extension: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
= Key Links =
= Overview =
* See the project [http://www.zachlipton.com/extensionStatus/ Status Page]
* [[Litmus:Extension/Notification|Notification system design]]


= Current Status =
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.
The [http://www.zachlipton.com/extensionStatus/ Status Page] (updated from time to time) has Zach's detailed task list, a broad overview is below:
* General
** Everything needs theming/styling/beautification
** <b>Content!</b>
* Feature Areas
** QMO Tab
*** Feeds are all being updated live from QMO, created a couple of custom QMO views for the various content areas
** Litmus Tab
*** Mockup and testcase retrieval are in place and working. Result submission is almost working
*** Need design and implementation for testgroup selection and other work in this area
** Bugzilla Tab
*** It's displaying a static page on QMO for now, need to write content (links to docs)
** Chat Tab
*** Chatzilla is bundled with the extension. Clicking the chat button launches a chat window and connects to irc
** Settings Tab
*** Preferences for Litmus account info and notifications are built and working. Litmus account gets validated before saving.
*** Need opsys/platform/locale settings
** Help Tab
*** Will be a static page hosted on QMO like the Bugzilla tab. Need content.
** Initial Setup
*** Mostly complete, have account creation, existing account login, settings
*** Settings needs a little more work
*** Account creation code needs to be secured
** Notifications
*** Specification complete and on the wiki. Need to implement and need to design Hermes (notification server)
 
= Initial Mockups =
See some screencaps at [http://zachlipton.com/qaExtensionMockups]


= Goals =  
= Goals =  
Line 41: 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...
= Key Links =
* Community aspects
* See the project [http://www.zachlipton.com/extensionStatus/ Status Page]
** Joga-style notification of special testing events, linking directly to the relevant set of tests and IRC
* [[Litmus:Extension/Notification|Notification system design]]
** Links to QMO resources that encourage people to get involved in other QA areas: bug days, bugzilla triage, etc...
 
= 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.
 


= 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 64: Line 41:
* Hermes - Notification server
* Hermes - Notification server
* Need a Greek name for the extension ;-)
* Need a Greek name for the extension ;-)


= Content pulled from external urls =
= Content pulled from external urls =
Line 77: Line 55:
* Notifications
* 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
** 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 =
Zach Lipton -- initial work, layout, notifications, bulk of the original code. Project member with CVS access.
Ben Hsieh -- Litmus tab, some layout improvements.
Zach Linder -- CSS, general theming.

Revision as of 18:50, 6 August 2007

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.

Key Links

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.


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 ;-)


Content pulled from external urls

  • QMO
    • Upcoming Events feed - the event feed
    • Recent forum posts feed - Pulled from an rss feed generated from a custom view that pulls the 10 most recent forum topics by creation date
    • The latest from QMO - Generated from the top post in the main RSS feed
    • How you can help! - Pulled from an rss feed that is automatically generated from this QMO page
  • Bugzilla
  • Litmus
    • extension.cgi and json.cgi (now landed in CVS)
  • Notifications

Current Contributors

Zach Lipton -- initial work, layout, notifications, bulk of the original code. Project member with CVS access. Ben Hsieh -- Litmus tab, some layout improvements. Zach Linder -- CSS, general theming.

Retrieved from "https://wiki.mozilla.org/index.php?title=Litmus:Extension&oldid=64689"