Space: Apache OpenOffice Community (https://cwiki.apache.org/confluence/display/OOOUSERS) Page: AOO 4.0 Testing Plan (https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Testing+Plan)
Edited by Ji Yan: --------------------------------------------------------------------- h1. AOO 4.0 Developing Mode h2. Trunk Stream The trunk stream is main stream in AOO 4.0 developing, all planned features and fixed bugs delivered in this stream, and final release code are also comes from it. You can get it from: https://svn.apache.org/repos/asf/openoffice/trunk h2. Branch Stream If a feature developing involves new UI or low level changes, it must be developed in a branch stream to reduce impacting to other features. You can get it from: https://svn.apache.org/repos/asf/openoffice/branches h2. Build Availability h3. Trunk Stream h4. Nightly build There is build bot services provide by Apache community, every night it build latest trunk stream code. If you need test trunk stream and don't want to build it by yourself, please get build from: http://ci.apache.org/projects/openoffice/index.html _Note: Build bot only provide a few language packages, e.g. English(US) and German, and there is no Mac OS build. So If you want to test other language or Mac, need to build it by yourself._ h4. Snapshot Build When milestone is approached, developer volunteer in community will get a specific revision trunk stream code and build it by themselves then name it as Developer Snapshot build, you can get it from: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds h3. Branch Stream Branch stream build will be provide by developer volunteer. h1. Test Activities h2. Test on Trunk Stream Following test activities will happen on trunk stream: # Build verification test # Performance verification test # System verification test # Defect verification # Feature test h2. Test on Branch Stream: In branch stream, if QA testing is required, QA volunteer will perform following test: # Feature test h2. Test on Developer Snapshot Build: When a developer snapshot build is ready, QA volunteer will perform following test: # Build verification test # Performance verification test # System verification test # Regression test h1. Test Method Generally, QA volunteer will do two kinds of test: automation test and manual test h2. Automation Test Following type of test will be executed automatically with # Build verification test # Performance verification test # System verification test # Regression test h2. Manual Test # Feature Test # Regression test h1. Feature Testing In AOO 4.0 release, following new feature/improvement will be implemented. As QA we will provide functional testing against feature area. The feature testing wil happen on trunk or branch stream it depends on feature deliveries to which stream. Following table indicate feature developing status and testing status as well. | *Component* | *Feature/Enhancement* | *Abstract* | *Development Status* | *Test Status* | | Interop | MS Office interoperability enhancements | Many MS Office interoperability enhancement and defect fixes across Writer, Calc and Impress. Here is the wiki of samples . For complete list, please refer to the query here. | In progress | | | Common | Accessibility support | integrate iAccessibiltiy2 support to improve the usability | In progress | | | | Performance improvements for loading and saving of documents | General performance improvements, especially on document loading and saving. The content of .odt and .odp files can be displayed before the whole document is loaded. Better usability by improved application response. | In progress | | | | Property Sidebar | A user interface improvement to allow easy and fast access to manage object properties. A concept to replace or as an alternative to toolbars. Task panes are used to allow more vertical space for the document area and to make use of current common wide screen displays. | In progress | | | | Patch Mechanism in Windows | Enable the patch mechanism in Window, so that AOO can provide small and accumulated patches to customers. | In progress | | | | More Gallery | Build in more cliparts from Symphony into the gallery | In progress | | | | Add Symphony gradients | when looking at Symphony I saw that there are some much nicer default gradients provided for user's convenience. Our current ones are medium usable (maybe created by developers), but still present in Symphony, too. To easily see what I'm talking about I have created two files: \- A Impress doc \- The same as png I propose to do the same as in Symphony: Add the lower symphony ones additionally. It's not much space (in the install set \;-)) and offers much nicer to-go gradients. Detailed proposal in dev mail here. | In progress | | | | Adopt palette to Symphony palette partially | Detailed proposal in dev mail here. | In progress | | | Common | "OpenOffice.org" \--> "Apache OpenOffice" | Adapt naming from "OpenOffice.org" (and its variants) to "Apache OpenOffice" | In progress | | | Writer | Interoperabilty improvement with MS Word on Table of Contents | The TOC data of a MS Word document is not parsed completely.And actual TOC data is from silently updating once a MS Word Document loaded.Thus,the fidelity can not be ensured especially when the document contents that impact TOC have been changed after creating TOC in MS Word.So,we propose to implement the TOC loading process to replace the update action. The tab between chapter number and TOC entry lost when loading a MS Word document,which leads to different gap between chapter number and TOC entry.That looks different from MS Word. Jump info will be lost when loading MS Word TOC created by un-checking "Use hyperlinks instead of page numbers". For this kind of TOC,end users can only press ctrl+mouse to click the page number of the TOC entry for jumping in MS Word. The customized character attributes will be lost when loading MS Word TOC created by un-checking "Use hyperlinks instead of page numbers". To this kind of TOC,the customized character attributes of the target paragraphs can be collected into TOC in MS Word. | In progress | | | Writer | Implement Draw features | Implement image rotation and some other existing draw features in Writer. | started | | | Draw (and others) | Fundamental changes needed for further bug fixing and features | Rework internal representation of drawing objects to use double precision and transformation matrix | started branch alg/AW080 | | h1. Routine Testing h2. Build Verification Testing Automation environment setup guide: [http://wiki.openoffice.org/wiki/QA/test_automation_guide] Automation BVT case list [https://svn.apache.org/repos/asf/openoffice/trunk/testgui/source/bvt/] h2. Performance Verification Test Automation environment setup guide: [http://wiki.openoffice.org/wiki/QA/test_automation_guide] Hardware requirement: CPU: Intel Core2 2.2 GHz Memory: 2 GB HDD: 40 GB free disk space Automation PVT case list [https://svn.apache.org/repos/asf/openoffice/trunk/testgui/source/pvt/] h2. System Verification Test Automation environment setup guide: [http://wiki.openoffice.org/wiki/QA/test_automation_guide] Hardware requirement: CPU: Intel Core2 2.2 GHz Memory: 2 GB HDD: 40 GB free disk space Automation SVT case list: [https://svn.apache.org/repos/asf/openoffice/trunk/testgui/source/svt/] h1. Regression Testing To make sure feature integrated and no regression issue introduced, after all feature developing is complete, QA will perform a suite of test cases composed by feature test cases and general functional test cases. h1. Bug Management AOO use bugzilla system for defect tracking http://issues.apache.org/ooo * New defect *# QA raise defect directly in bugzilla system, and change its status to "CONFIRMED" *# QA confirm community volunteer opened defect which status is in "UNCONFIRMED" * Verify defect When defect is fixed, QA install latest build and follow reproduce steps to verify whether defect is fixed or not. h1. Test Case Management In AOO 4.0 release, we use Test Link system to manage test case and test execution http://aootesting.adfinis-sygroup.org QA write new feature test case and put it in test plan, after feature is complete developed QA executed in assigned platform. h1. Non-functional Requirement QA will testing AOO 4.0 release against following testing platform Major testing platform: Windows XP 32-bit Windows 7 32-bit/64-bit Windows 8 32-bit/64-bit RedHat Linux 6 32-bit/64-bit SuSE Linux 11 32-bit/64-bit Ubuntu 12.04 32-bit/64-bit Mac OS X 10.6/10.7/10.8 Additional testing platform: FreeBSD Solaris OS/2 Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action
