UnoAPITest/project/cwsTests
From Apache OpenOffice Wiki
This project accompanied the way of UnoAPITests to be mandatory CWS tests.
Project Plan
develop concept and identify needing tools | in progress | M1 |
basic console script checkcws | planned | M2 |
query EIS for added modules | planned | M3 |
deliver status to EIS | planned | M4 |
automatic Office installation | planned | M5 |
Bugfixing | planned | M6 |
Milestone | Due |
M1 | End of Dec. 07 |
M2 | Mid of Jan. 08 |
M3 | End of Jan. 08 |
M4 | Mid of Feb. 08 |
M5 | End of Feb. 08 |
M6 | End of Mar. 08 |
Concept of mandatory UnoAPITests for CWS
CWS is ready
If the CWS is ready the developer has to run checkcws. checkcws calls an UnoAPITest for all modules which are added to the cws. If the result is FAILED the developer has
- to fix the failure inside the implementation
- to get an exception
To get the later one the developer must have good arguments why he/she is not able to fix the implementation.
If the UnoAPITest works fine with state state OK the CWS could be set readyForQA
Exception
If an exception is approved, the developer has to do the following:
- write a new Issue
- update $MODULE.sce and knownissues.xcl