How can you helpThe are several possibilities for you to help improving this project.
Your mission is discovering issues inside the Office API or the test harness itself? Feel encouraged
to make heavy use of the given frame work and if you find a failure, please write an issue
with a title as follows:
API: component::interfacefor API issues. And
e.g. API: SwXBodyText::XText
qadevOOo: <title>for issues regarding the test harness.
In both cases the component is 'api' and they should be assigned to firstname.lastname@example.org
You want to extend the testcases and add the missing ones, then feel highly encouraged to
check out the sources and extend the functionallity of the testcases.
If you wonder which testcases still might be missing take a look at the List of missing testcases. If you are unable to check in your changed sources feel free to mail them to email@example.com.
Those who develop own components for the Office will find the harness useful for
testing purposes. We'd like to get information and feedback to be able to enhance
our harness, and we would also like to add the testcode written by you to future automated test runs
when your component finally found its way in the Office.
The Scripting Framework Team already makes use of this.
- We are sure that our test harness is useful for developers of other applications that provide an API, too. We'd like to get feedback if you made use of it and if you'd like to have any useful extension to it.
Last Modified: $Date: 2004/03/10 15:58:38 $