Difference between revisions of "Test Refactor"

Revision as of 03:24, 25 June 2012

Current 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. The summary is here.

• test

Includes reusable code for UNO API test.

• 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 modules for testing.

• testcommon

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

• qadevoo

UNO API Test/Complex Test. Need to refactor the old test code to JUnit 4. It depends on testcommon.

• testscript

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

Todo for the existing modules.

• test

Replace it with testcommon

• testgraphical

Re-implement it as JUnit4 testcase in testscript.

• testautomation

Convert the scripts as JUnit4 testcases in testscript. And remove it when testscript is enough.

• smoketestdoc

Move it into testscript.

• smoketestoo_native

Re-implement it as JUnit4 testcase in testscript.

Next Step

In order not to break build, suggest to create the three new modules firstly. Then migrate the legacy code into the new structure steps by steps. When it works stably, we can remove all the old modules.