Difference between revisions of "UnoAPITest/project/cwsTests"

Revision as of 14:05, 19 December 2007

This project accompanied the way of UnoAPITests to be mandatory CWS tests.

Project Plan

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 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

Exception handling

TODO

checkcws

checkcws is an commandline script similar to [[CheckApi|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

Notes

• only pro versions
• named pipes for connecting the office with pro+platform

Automatic Office installation

As the SmokeTest the checkcws should be able to install the office automatically.
$SOURCE_ROOT should be the setup root

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
    • therefore EIS needs a new Interface -> User:bei
  • 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
• change default connection string from socket to named pipes
• 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