Hi Andrew, > In looking at the files in the source directory for dbaccess I find some > testing related files. But these are narrow in regards to backends, it > appears on the biblio dbf file is ues, and constrainted in what is > tested. So I was wondering how I might help with this, if would put > together some test scripts how would I go about offering them into the > project. > > Is there a SOP for test script productio, for example it appears that an > automated tool is being used and capturing output. Does this require > then that the tests all be produced in Java?
seems you already decided on your next steps here (helping with what the French community started), but let me (in short) shed some light on the existing test infrastructure. In general there's an application called TestTool, which can be used to write and run Basic scripts, simulating user interaction in an running OpenOffice.org instance. This approach really simulates how users interact with the application - you can do mouse clicks, keyboard input, and the like. I am not sure how many Base-related scripts actually exist (except in our Sun-internal QA). For this question, and questions regarding the TestTool in general, I'd like to direct you to the QA project, [EMAIL PROTECTED] in particular. Second, there's a number of tests which are for the UNO API. Those use a Java framework, and basically do somethine like: Connect to a running OOo instance, instantiate some components, and do some tests with them. Probably this is what you found in dbaccess/qa. This part again splits into some generic mere interface tests (e.g., if a component has certain interfaces, it's verified that this sole interface works as expected. Additionally, there are so-called complex or integration tests, which do more, well, complex test cases. All test approaches have their advantages and disadvantages. Coming from the user's end (TestTool) helps finding bugs in the "higher layers", coming from the API side (<module>/qa) helps finding bugs in the core implementations, which might or might not ever manifest at the user interface. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
