Calendar:QA Chat:2006-10-12: Difference between revisions

Revision as of 16:02, 12 October 2006

Feel free to add your own ideas

Assign a notetaker - someone responsible for putting the meeting log up on this wiki page afterward.
0.3 has shipped!
Next week's meeting will be a post-mortem QA on the 0.3 release. (What could we have done better, what did we do well, etc).
Next test day will be Tuesday, October 17.
- What should we focus testing on for Tuesday's test day?
- Who would like to update the Test Day wiki? (It's largely cut and paste from the previous test day).
- What hours should the test day run?
With a test day every two weeks, we will have one on Halloween day (31st). Clint has some wacky ideas about that, and needs your perspective.
Regression tests - is anyone interested in putting one together?
- jminta has a framework together for a calendar-qa extension which provides a good way to run specific ICS based test cases, particularly if you are hunting down a regression range.
- We need to search through bugzilla, finding problem ICS data, get those events into a list for any regression strategy we choose.
- There are some basic XPCShell tests in calendar/test that we can look into extending if we want a more "automatic" regression solution.
Put the Calendar QA Todo list together.

@@ Line 20: / Line 20: @@
 * With a test day every two weeks, we will have one on Halloween day (31st). Clint has some wacky ideas about that, and needs your perspective.
 * Regression tests - is anyone interested in putting one together?
-** jminta has a basic framework together that can run ICS files through XPCShell to do basic regression testing. This is probably a good place to start and we can extend this.
+** jminta has a framework together for a calendar-qa extension which provides a good way to run specific ICS based test cases, particularly if you are hunting down a regression range.
-** Get/Find jminta's code
+** We need to search through bugzilla, finding problem ICS data, get those events into a list for any regression strategy we choose.
-** Search through bugzilla, finding problem ICS data, get those events into a list.
+** There are some basic XPCShell tests in calendar/test that we can look into extending if we want a more "automatic" regression solution.
-** Extend the XPCShell test if needed?
-** Integrate this test with Tinderbox builds once it is finished.
 * Put the [[Calendar:QA_TODO|Calendar QA Todo list]] together.