[Cosmo-dev] Cosmo QA process alterations

[Matthew Eernisse]

Comments below ...

Aparna Kadakia wrote:
> 3. Another change in the process we would like is for QA to work on 
> automating new features in the branch they are developed in before that 
> feature is dropped in to the trunk. The next 2 releases may potentially 
> have big features like calendar overlays, month view and date picker. We 
> would much rather devote the time to writing more automated tests for 
> these features upfront rather than playing catch up in following 
> releases or during the release certification and resorting to manual 
> testing to cover what we couldn't squeeze in.

I've created a branch for my overlay work here:

svn+ssh://svn.osafoundation.org/svn/server/cosmo/branches/mde_overlay_2007-10-15/

Most everything is working now, with the single exception (that I know 
of so far :)) of removing recurring items that exist in multiple 
collections -- basically I need to disable the All Future Items option 
in that case. Obviously more things will shake out as we bang on it for 
awhile.

> 4. Ideally developers can write very basic workflow testcases for UI 
> features along with their unittetss before QA steps in to cover the more 
> intricate working scenarios. This will ensure that QA has everything it 
> needs and is not blocked in any way when taking on a feature to 
> automate. This will all insure a higher quality of the feature when it 
> lands in trunk.

Now that I've got the basic functionality done, the next thing is to 
start working on some tests. One known deficiency of the JS test 
framework in Windmill is Safari support, which I'll take a look at in 
the next day or so.

Thanks.


Matthew