Calendar:QA Chats: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
***Investigation into Regression/Unit test systems | ***Investigation into Regression/Unit test systems | ||
***Add your own idea here... | ***Add your own idea here... | ||
*How do developers alert the QA community to a new feature or recently completed fix | |||
**Use the VERIFIED and RESOLVED status in bugzilla | |||
**General calendar QA mailing list that can be "watched", perhaps via bugzilla. | |||
**Use status whiteboard portion of a bug | |||
**Other options? | |||
*Brainstorm how to build a viable calendar QA community | *Brainstorm how to build a viable calendar QA community | ||
**Getting direction from the mozilla staff | **Getting direction from the mozilla staff | ||
**Directly inviting people that posted to the NG saying "so I was testing Sunbird/Lightning..." | **Directly inviting people that posted to the NG saying "so I was testing Sunbird/Lightning..." | ||
**These Chats? | **These Chats? | ||
Revision as of 19:41, 28 June 2006
<< Back to Calendar QA Home Page
We will hold regular, semi-informal chats once a week to allow people interested in calendar QA an opportunity to connect with each other and discuss calendar QA topics. This first meeting will serve to lay the groundwork for the set of work we will do leading up to the 0.3 release. The meeting will last no longer than an hour.
Meeting Details
- June 29th, 2006 at 16:00UTC
- Find the time in your timezone
- Meeting will be online using IRC at: irc://irc.mozilla.org/calendar-qa
Proposed Talking Points -- feel free to add your ideas
- From the QA Goals outlined in the QA Aspect newsgroup post:
- Discuss How to Begin the Effort
- Testcase creation - perhaps using the user scenarios as a starting point
- Investigation into Regression/Unit test systems
- Add your own idea here...
- Discuss How to Begin the Effort
- How do developers alert the QA community to a new feature or recently completed fix
- Use the VERIFIED and RESOLVED status in bugzilla
- General calendar QA mailing list that can be "watched", perhaps via bugzilla.
- Use status whiteboard portion of a bug
- Other options?
- Brainstorm how to build a viable calendar QA community
- Getting direction from the mozilla staff
- Directly inviting people that posted to the NG saying "so I was testing Sunbird/Lightning..."
- These Chats?