Difference between revisions of "UnoAPITest/project/cwsTests"
m (→CWS is ready) |
B michaelsen (Talk | contribs) m |
||
| Line 272: | Line 272: | ||
[[Category:API]] | [[Category:API]] | ||
[[Category:UnoAPITest]] | [[Category:UnoAPITest]] | ||
| − | [[Category: | + | [[Category:CWSQAStatus]] |
Latest revision as of 11:19, 26 October 2009
This project accompanied the way of UnoAPITests to be mandatory CWS tests.
Contents
Project description
The goal of the project is to set up a mechanism to find regression in the API on a cws. This should be done by run the UnoAPITests on added modules to a cws. In mostly all modules which support UnoAPI exist a qa/unoapi folder. This folder contains a make file which starts the UnoAPITests related to this module.
To make it easy a simple script, f.e cwscheckapi (in coherence to checkapi) should do this job.
Project Plan
| develop concept and identify needing tools | done | M1 |
| basic console script checkcws | done | M2 |
| query EIS for added modules | done | M3 |
| automatic Office installation | done | M4 |
| deliver status to EIS | done | M5 |
| Bugfixing | started | 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 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 knownissues.xcl
Exception handling
TODO
CwsCheckApi
cwscheckapi is an commandline script similar to checkapi. The runner query EIS for all added modules relayed to the CWS and execute the tests.
Issue 85368
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
Notes
- only pro versions
- named pipes for connecting the office with pro+platform
- add solenv to a cws and commit checkws in solenv/bin
Automatic Office installation
Notes
- As the SmokeTest the cwscheckapi should be able to install the office automatically.
- the smoke test has no separate installation routine. It's much easier to install the office via UserlandScripts.
- $SOURCE_ROOT could be the setup root entry
- $SHIPDRIVE indicates the path to the seups of a master office
- $CWS_WORKSTAMP indicates a cws envirnment
- $SOL_TMP indicates a local environment
- support of local environments
Install-Sets
| |
|
|
| |||||
| |
|
|
| |||||
| setsolar | |
|
||||||
| |
|
|||||||
| setcws | ||||||||
| |
|
|||||||
| ooO-Env.Set | ||||||||
| local env. | ||||||||
Userland-Scripts
- setsolar
- $SHIPDRIVE/$INPATH/UserScripts/$PKGFORMAT/{OfficeVersion}/install
- setcws
- $SOLARVERSION/$INPATH/bin$$UPDMINOREXT/userscripts/install
EIS
- communication via SOAP
- the EIS should display test runs
- currently some tests attach result files to the CWS, f.e. PerformanceTests
- the EIS should have a extra data base for CWS tests
- the EIS should display successfully executed tests with a green bullet
- the EIS should support the possibility to set the "OK" status manual. See #runner
runner
first step
The developer at Sun/StarOffice have some privileges that other don't have. This is f.e. an easier access to EIS.
- SOAP-Interface needet
- SOAP has too many dependencies. So cwsquery will be used.
- runner: change default connection string from socket to named pipes if possible
- complex Test complex.unoapi.CheckModuleAPI must be stabilized
second step
The SOAP-Interface of EIS needs https connections.
- implement https for community developer
- implement user/password login into EIS
