QA/TCM: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
Line 132: Line 132:
|-
|-
| 0.8
| 0.8
|
*Django to DB
*UI once-over for consistency
| 2/3/1012
|-
| 0.9
|  
|  
*Final feature implementation push
*Final feature implementation push
*Security review
*Security review
| 3/15/1012
| 3/15/1012
|-
| 0.9
|
*Django to DB
*UI once-over for consistency
| 2/3/1012
|-
|-
| RC  
| RC  

Revision as of 18:10, 25 January 2012

Case Conductor

Summary

QA has been using litmus.mozilla.org for the past 5-6 years and it's serviced the community semi-appropriately during that time. Unfortunately, as the community plans to scale up, the current codebase is not an appropriate fit and needs to be replaced by a better scalable tool in terms of usability and functionality.

Mission Goals

  1. Replace litmus.mozilla.org with a more modern tool
  2. Build a more intuitive and useful manual testcase manager
  3. Offer a better extensibility to interface with other tools

Weekly Meeting

  • Every Tuesday @ 11:00am Pacific Time
  • +1 650 903 0800 x92 Conf# 490 (US/International)
  • +1 416 848 3114 x92 Conf# 490 (Canada)
  • +1 800 707 2533 (pin 369) Conf# 490 (US Toll Free)
  • join irc.mozilla.org #tcm for backchannel discussion

Team

  • PM & QA
    • Cameron Dawson [:camd]
  • Second in QA
    • Rebecca Billings [:rbillings]
  • QA
    • Matt Brandt [:mbrandt]
  • Django Dev
    • Carl Meyer [:carljm]
  • UI Designer
    • Eric Meyer [:ericam]
  • JavaScript Dev
    • Jonny Meyer [:jonnygm]

Contribute

We need your help to make sure TCM is equal or better than Litmus in every area we need in QA.

To help, you can:

  1. Think about your current workflow with Litmus
  2. Check out the staging site and play with it
    1. Please keep in mind it's under development and incomplete
    2. Some areas are only "wireframes." If you see a tab at the bottom of the page that says, "wireframe" or "incomplete" then odds are it's not functional, just to show how it WILL look.
  3. If there's something missing (remember it's not done yet) then check TCM Tracker to see if we plan to address it. If you don't want to check tracker, that's ok. I can do some vetting.
  4. Enter a user story! Enter the story in Bugzilla first, and I will vet it, and prioritize it in Tracker. Your workflow matters!

Or if you'd rather just chat about it, that's great too. Please come find me (Cameron) and we'll talk.

Resources

Staging Site cc.oddsites.net
User Stories CC Tracker
Enter Story New User Story
IRC #caseconductor on irc.mozilla.org
Blog Blog
Forum Google Group


Planning Documents

Product Management

You can view the current state of the user stories here:

Note: New user stories and bugs are entered in Bugzilla first. Then Tracker will import them and we will prioritize them. This allows people to watch progress in Bugzilla as well.

Planned Releases

Milestone Milestone Focus Feature Complete
0.3
  • Results
5/25/2011
0.4
  • Product mgmt
  • User mgmt
  • Test mgmt
  • Environment mgmt
6/20/2011
0.5
  • More mgmt work
  • Running tests
  • Litmus to TCM migration tool
09/30/2011
0.6
  • More running tests
  • More test mgmt
11/1/2011
0.7
  • Authentication
  • Community mgmt
  • Final Platform release
11/15/2011
0.8
  • Django to DB
  • UI once-over for consistency
2/3/1012
0.9
  • Final feature implementation push
  • Security review
3/15/1012
RC
  • release it
3/31/2012


Information

General

Technical

Marlena's brain dump about testing with tcm's and wikis