[Chandler-dev] Test Plans and RC

[Philippe Bossut]

Hi,

We had our Bug Council this afternoon and the good news is: RC4 is 
holding water! No new bug worthy of a new RC was logged. This is very 
good. Another couple of days like that, and we'll be able to declare 
victory and create a final official build.

We need however to hit another milestone before getting there: doing a 
thorough pass through the whole test plans 
(http://chandlerproject.org/Projects/ChandlerDesktopTestSpecifications). 
We need *everyone* to help on this and test and update the test matrices.

To make this easier and avoid duplicating work, the plan have been 
assigned to devs. Thanks to those who updated the matrices with their 
results. If you haven't done so yet, please, please *update the pages as 
soon as possible* so that we can review this Tuesday morning.

The exit criteria is that *all tests* need to be passed once or logged 
with a bug that's reviewed by the Bug Council so that we know exactly 
what we ship.

The test plans coverage is pretty good right now but we need help on the 
recurrence ones: those are massive plans. We currently have 6 persons 
working on various sections of it (Jeff, Katie, Philippe, Mikeal, Dan, 
Adam). We decided during the Bug Council that, in order to reduce the 
number of cases, we'll limit ourselves to testing the daily and weekly 
recurrence cases under the assumption (and experience) that "daily" is 
the case that creates the most issues and that "weekly" is the most used 
user case. Test "biweekly" and "monthly" only if you have time. Testing 
"yearly" for sure is a little far fetched.

Before taking over a section though, check on IRC #chandler with one of 
assigned person (see on the wiki who's assigned to the 4 sections: 
http://chandlerproject.org/Projects/ChandlerDesktopTestSpecifications) 
so we don't duplicate our efforts.

Knocking down those test cases is a great way to reduce the wait to 
final release and make us more confident. Thanks all for your help.

Cheers,
- Philippe