I have updated my previous blogpost with links to the project testing plan, but I thought it would be better to have a separate blogpost to keep track of the testing and QA work.
For the detailed Testing plan please see (http://code.google.com/p/weave-mailnews-sync/wiki/TestPlan?ts=1279537331&updated=TestPlan)
QA Day 1 (19th July):
Completed testing with Config 01. None of the tests failed but 5 issues were reported that need fixing.
QA Day 2 (23rd July):
Completed testing with Config 02. No new issues reported. Custom tag sync (http://bit.ly/cayX3L) was also tested between the Windows 7 and Ubuntu 9.04 machines.
Monday, July 19, 2010
Thursday, July 15, 2010
GSoC 2010 Mid term evaluations
Mid term evaluations are here and I hope to have a progress meeting with my mentor to get his detailed feedback on the project.
I have packaged the MailNews sync engine into an xpi file and uploaded it to the mailnews sync project site (http://code.google.com/p/weave-mailnews-sync/downloads/list). It requires Firefox 1.4 (https://addons.mozilla.org/en-US/firefox/addon/10868/) to work (it is basically an extension of an extension!). The MailNews Sync extension currently syncs status, flag and tag data of Feed and Newsgroup items between different Seamonkey instances. I tested it on Seamonkey 2.0. I couldn't test it on Seamonkey trunk 2.1 yet but I'm hoping that everything will work smoothly there as well. Since comm-central build is not working (sm tinderbox is having a few hot days..) I will test with currently available nightly build.
Few things left to be done this week:
- Decide on a solid test plan for MailNews sync engine
- Start testing and bug fixing for mailnews engine
Update!
I have posted the MailNews engine test plan to the project site ( http://code.google.com/p/weave-mailnews-sync/wiki/TestPlan?ts=1279510088&updated=TestPlan ). Testing will be done using 4 configurations.
Week 1 (18th to 24th July) :Config 01&02
Week 2 (25th to 31st July) : Config 03&04
All issues will be reported and tracked on http://code.google.com/p/weave-mailnews-sync/issues/list.
Testing begin today!
I have packaged the MailNews sync engine into an xpi file and uploaded it to the mailnews sync project site (http://code.google.com/p/weave-mailnews-sync/downloads/list). It requires Firefox 1.4 (https://addons.mozilla.org/en-US/firefox/addon/10868/) to work (it is basically an extension of an extension!). The MailNews Sync extension currently syncs status, flag and tag data of Feed and Newsgroup items between different Seamonkey instances. I tested it on Seamonkey 2.0. I couldn't test it on Seamonkey trunk 2.1 yet but I'm hoping that everything will work smoothly there as well. Since comm-central build is not working (sm tinderbox is having a few hot days..) I will test with currently available nightly build.
Few things left to be done this week:
- Decide on a solid test plan for MailNews sync engine
- Start testing and bug fixing for mailnews engine
Update!
I have posted the MailNews engine test plan to the project site ( http://code.google.com/p/weave-mailnews-sync/wiki/TestPlan?ts=1279510088&updated=TestPlan ). Testing will be done using 4 configurations.
Week 1 (18th to 24th July) :Config 01&02
Week 2 (25th to 31st July) : Config 03&04
All issues will be reported and tracked on http://code.google.com/p/weave-mailnews-sync/issues/list.
Testing begin today!
Thursday, July 8, 2010
Sync services become part of the mozilla platform
With Bug 571902 the weave sync services have now been integrated into the mozilla platform by the weave developer team. The sync code can now be found in the mozilla-central repo under services/. Look forward to seeing Seamonkey include sync as a service in a future release. My GSoC project mentor KaiRo has reported Bug 576970 to get the sync UI ported into Seamonkey (comm-central repo). Although landing sync code in mozilla platform means the application specific code has been separated (mainly ui code) there is still app-specific code in the services/sync which is why I still need my tabs sync patch for Seamonkey to be approved by the Weave team.
Work done last week:
1. Updated my patch for getting tabs sync to work in Seamonkey to include new weave code changes.
2. Started a new mercurial repo to track changes I make to the weave code.
https://bitbucket.org/hariniachala/sm-weave
Learned a lot about mercurial in the process.
3. Changed mailnews extension code to sync both feed and newsgroup mailheaders (status and tags). I am using a svn repo for the mailnews extension.
http://code.google.com/p/weave-mailnews-sync/
Work to be done:
1. Sync mailnews engine by default on application startup.
2. Create a testing plan for testing new mailnews engine in Seamonkey & Thunderbird.
3. Update mercurial repo with mailnews code.
4. Track Bug 576970 and see how sync can be ported into Seamonkey!:)
During this time I discussed with KaiRo on some aspects of the project. It was decided that all weave development for Seamonkey should be tested with Seamonkey trunk code. It was also decided to continue development of mailnews engines as a separate extension.
Work done last week:
1. Updated my patch for getting tabs sync to work in Seamonkey to include new weave code changes.
2. Started a new mercurial repo to track changes I make to the weave code.
https://bitbucket.org/hariniachala/sm-weave
Learned a lot about mercurial in the process.
3. Changed mailnews extension code to sync both feed and newsgroup mailheaders (status and tags). I am using a svn repo for the mailnews extension.
http://code.google.com/p/weave-mailnews-sync/
Work to be done:
1. Sync mailnews engine by default on application startup.
2. Create a testing plan for testing new mailnews engine in Seamonkey & Thunderbird.
3. Update mercurial repo with mailnews code.
4. Track Bug 576970 and see how sync can be ported into Seamonkey!:)
During this time I discussed with KaiRo on some aspects of the project. It was decided that all weave development for Seamonkey should be tested with Seamonkey trunk code. It was also decided to continue development of mailnews engines as a separate extension.
Subscribe to:
Posts (Atom)