QA/TCM: Difference between revisions
(→Team) |
|||
| Line 27: | Line 27: | ||
<br> | <br> | ||
== Contribute == | == 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: | |||
# Think about your current workflow with Litmus | |||
# Check out the staging site and play with it | |||
# If there's something missing (remember it's not done yet) then check 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. | |||
# Enter a user story! Your workflow matters! | |||
Or if you'd rather just chat about it, that's great too. Please come find me and we'll talk. | |||
== Resources == | == Resources == | ||
Revision as of 23:05, 13 May 2011
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
- Replace litmus.mozilla.org with a more modern tool
- Build a more intuitive and useful manual testcase manager
- Offer a better extensibility to interface with other tools
Team
| PM & QA | Cameron Dawson [:camd] |
| 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:
- Think about your current workflow with Litmus
- Check out the staging site and play with it
- If there's something missing (remember it's not done yet) then check 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.
- Enter a user story! Your workflow matters!
Or if you'd rather just chat about it, that's great too. Please come find me and we'll talk.
Resources
| Staging Site | tcm.oddsites.net |
| User Stories | TCM Tracker |
| Enter Story | New User Story |
| IRC |
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 |
|
5/25/2011 |
| 0.4 |
|
6/20/2011 |
| 0.5 |
|
tbd |
| 0.6 |
|
tbd |
| 0.7 |
|
tbd |
| Beta | fix it | tbd |
| RC | release it | tbd |
Information
General
Technical
- TCM Front-End code is located on on Github.
- TCM Platform code is located on on Github.
- Bugs can be filed using a handy form
- To see a list of already filed bugs, please take a look at a generic query for the TCM component
- Hudson Status for platform and automation