Actionlist for fixed Issues
Common requirements
Check existence of Spec for Feature/Enhancements (see http://specs.openoffice.org)
Check existence of feature mail for Feature/Enhancements (see http://www.openoffice.org/servlets/SummarizeList?listName=allfeatures)
Check if the target of the issue is set according to the target of the CWS
Interactions with other OOo components
Identify possible risks
Identify possible dependencies with other OOo applications
Provide information to respective QA stake-holders
(e.g.
file QA-child task respective dependency issue. Ideally add those to the
respective CWS.)
Provide information at QA mailing list dev@qa.openoffice.org
Flags for CWS
Test cases specifications/Auto test scripts
Check existence of test cases in TCM - Test Case Management (Login to TCM)
Check existence of automated test scripts (find the existent Bas-Files / List of all Tests for 2.0.4)
Enhance old test cases if necessary
Create new test cases if necessary
Create task for appropriate auto-tester if necessary
Actions
Verify fix on (at least) two platforms
Verify issue against Spec and Feature mail
Run reasonable automated tests with VCL TestTool (at least run first.bas, topten.bas from framework/first)
Enroll test case/automated test
NOT FIXED
Contact developer
Inform QA-Representative and Owner of CWS
Reassign issue to developer, include a note into the issue and make sure the issue has been set to NEW
Add additional information about rejection in decription field for this CWS in EIS
Helpful Links
EIS - automatic guest login - : http://eis.services.openoffice.org/EIS2/GuestLogon
EIS - general user login - : http://eis.services.openoffice.org/EIS2/Logon
IssueTracker - search for ID - : http://qa.openoffice.org/servlets/ProjectIssues
Specification process : http://wiki.services.openoffice.org/wiki/Category:Specification
