Difference between revisions of "UnoAPITest/project/cwsTests"
From Apache OpenOffice Wiki
< UnoAPITest | project
(new checkcws) |
(add: Flowchart picture) |
||
| Line 70: | Line 70: | ||
==Concept of mandatory UnoAPITests for CWS== | ==Concept of mandatory UnoAPITests for CWS== | ||
| + | [[Image:UnoAPITest CWS flowchart.png|thumb|Flowchart for mandatory UnoAPITests in CWS]] | ||
=== CWS is ready === | === 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 | 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 fix the failure inside the implementation | ||
Revision as of 13:26, 5 December 2007
This project accompanied the way of UnoAPITests to be mandatory CWS tests.
Contents
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 treatment
If an exception is approved, the developer has to do the following:
- write a new Issue
- update $MODULE.sce and knownissues.xcl
checkcws
checkcws is an commandline script similar to checkapi. It query EIS for all added modules relayed to the CWS and execute the tests.
Command line parameter
- -m Module[,Module]
- add the given modules to the test
- -log true
- enhance the logging output
- -debug true
- enabled the debugging mode: enhancing of output
- -tdoc Test-Document-Path
- path where testdocuments could be found
- -KeepDocument
- the tests normally close the documents which opened for testing purposes. If this flag is set to true all documents are available at the end of the test.
- -ini RunnerProps
- path to property file for CheckAPI. Default: $HOME/.runner.props
