Cwscheckapi

To avoid regressions in the UnoAPI CwsCheckApi must be executed as final step on cws handling.

Concept of mandatory UnoAPITests for CWS

Flowchart for mandatory UnoAPITests in CWS

CWS is ready

If the CWS is ready the developer has to run cwscheckapi. 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 treatment

If an exception is approved, the developer has to do the following:

• write a new Issue
• update $MODULE.sce and/or knownissues.xcl