Difference between revisions of "Test Refactor"

Revision as of 07:15, 21 June 2012

Current Testing Status

Currently, there are many modules for testing. Note, the mentioned testing here requires a running OpenOffice instances. That means OpenOffice must be installed before testing. It's not the unit test at the code level.

• test

Includes reusable code for UNO API test.

• testtools

Some tests for UNO bridges and language bindings.

• testgraphical

Test tool to test documents by it's graphical representation.

• testautomation

All test scripts for the old VCL Testtool. Nobody maintains it now.

• smoketestdoc

It's used to generate the test documents required by smoke test.

• smoketestoo_native

A small test suite to verify if the basic functions of OpenOffice.org work.

• qadevOOo

UNO API test, complex test.

Target

The target is to reduce module count and organize the testing code clearer. Suggest to keep only 3 directories for testing.

• testcommon

The reusable code for testing. Not include any test case.

• testuno ?

UNO API / Complex test cases should be written in the module. It depends on testcommon.

• testscript or testgui?

GUI test cases should be written in the module. It depends on testcommon.

The detail:

• test

Replaced by testcommon

• testtools

Replaced by testcommon

• testgraphical

Re-implement it as JUnit4 testcase in testscript.

• testautomation

Removed.

• smoketestdoc

Move it into testscript.

• smoketestoo_native

Re-implement it as JUnit4 testcase in testscript.

• qadevOOo

Change the name to testapi?