Monday, 25 May 2009
Monday, 25 May 2009
EIS just got a couple of new features.What´s new is that there are now a couple of tests that can be done on a OpenOffice.org ChildWorkspace which each have a status which is used to caclulate an overall status for the OpenOffice.org ChildWorkspace. Tests are either short test which are run automatically by EIS each time the user visits the new "Tests" tabpage of a ChildWorkspace or are longer running tests which are queued for execution on dedicated test computers. The short automatic tests do test such things like if all tasks at the ChildWorkspace are already fixed or if the release set at the ChildWorkspace is allowed for the MasterWorkspace the ChildWorkspace is based on. Longer running tests queued for execution on dedicated computers are AutomationCAT-0 tests, ConvWatch-Tests and Performance Test. Additionally also a couple of buildbots have been integrated which do now report their status of the build back to EIS. For tests being queued to dedicated computers to be run on this does mean that you might have to wait some time more for the results because tests on other ChildWorkspaces might be before yours in the queue. On the other hand using dedicated machines for the tests does make tests better comparable and does eliminate some problems we currently have with running automated tests on different hardware.
these tests are run on dedicated computes, they need approximately 8 hours and use the VCLTesttool with a couple of selected test scripts (called the CAT-0 tests) to check the quality of an OpenOffice.org installation. At the end of the test the status is in EIS is set to "finished needs review" and a link to QUASTe is being provided where the QA Rep can look at the details of the many testscript results and after review can finally set the status for the test in EIS to "ok" or "failed".
these tests are also run on dedicated computers, they need round about 15 minutes and do compare loading of some sample test documents and startup of OOo modules without opening a document for an OpenOffice.org of the current ChildWorkspace with the result of the same tests for an OpenOffice.org of the corresponding MasterWorkspace. At the end of the test the status is reported back to EIS and also an attachment has been save on the ChildWorkspace which contains details about the tests. This is done to find potential regressions in performance on a ChildWorkspace. The test has some tolerantable difference in performance that is allowed and could as well be cause by other factors than those in responsibility of the source code changes on the ChildWorkspace. AutomationCAT-0, ConvWatch and Performance tests currently need to be able to find installation sets for the CWS on Suns internal network. But if you are a Sun-external QARep of a ChildWorkspace owned by a Sun developer you can now also start these tests. We are in the process of considering how a integration of ChildWorkspaces where the owner is not a Sun developer could look like, stay tuned.
these test are also run on dedicated computers and need between 2 and a half and 3 hours to run. Here a couple of test documents are loaded, than printed to a postscript file and the postscript file is than converted to a graphics file. This is done for the OpenOffice.org of the ChildWorkspace and the corresponding MasterWorkspace. Graphics from the MasterWorkspace OpenOffice.org are than compared to those from the ChildWorkspace OpenOffice.org to find potential regressions in the layout engines and import filters.
As you can see in the picture below the new "Tests" tabpage in EIS contains the overall result and a table with results for individual tests and buttons to start tests.
there is an automatic test for wether a tool called cwslocalize has been called on a ChildWorkspace to calculate translation word count for the ChildWorkspace. This tool is not yet available to Sun external developers. This is being worked on.
The OOo Wiki contains some more details and there is also a "TestBots a first steps" announcement on the QA Mailinglist from Jörg Jahnke.
tags: automation cat0 development eis openoffice.org qa test testtool tools webapplication
Friday, 23 May 2008
Due to a fix to i89840 the cwsquery commandline tool changes incompatible.
Previously for most commandline parameters the result was provided on standard output and when it was a list just one item per line was printed and some additional information was given before that list on standard error. Some commandline switches did it differently tough and provided the result as a comma separated list on standard error. The later ones have now been changed to also use the other method of printing the result.
The fix for the issue has been done in the OpenOffice.org ChildWorkspace cwsqueryenhance3 and will be active in one of the next milestone. If you have created yourself some scripts where you call the cwsquery tool and parse the output these might eventuall need to be changed.
tags: cws cwsquery eis openoffice.org
Thursday, 20 Dec 2007
In the past months we often heard complaints about the sluggish performance of some pages in the Environment Information System (EIS). If you are a regular user of the tool, then you should hopefully have noticed that the performance has improved in the past few weeks.
There were two steps we took. First and foremost Bernd Eilers optimized the caches of the database used by the application. This has a positive effect on all pages that retrieve larger amounts of data from the EIS database. Another optimization was to reduce the amount of data presented on the Child Workspace overview page, one of the most used pages of the application. This page now has tabbed folders which can be used to select the different sections, like attached issues or the tinderbox status, of the page instead of retrieving and displaying all data on one page:
These were relatively simple changes but they have a very positive effect on the performance of the tool. Should there be other areas which you think should be improved, then just let us know. The best place to raise such issues is the dev@tools.openoffice.org mailing list.
tags: eis openoffice.org tools
Thursday, 02 Aug 2007
A new website http://tools.services.openoffice.org is there as a home for Web Applications offering services for OpenOffice.org which will hosts EIS and a new Dashboard Web Application. The start page also offers Links to the OpenOffice.org Wiki, the CodeSnippets and QATrack for convienience. The new Dashboard Web Application shows some statistical data provided by OpenOffice.org committees about OpenOffice.org website usage.
tags: eis openoffice.org tools
Wednesday, 07 Mar 2007
Lars Oppermann recently started the odf4j (odf for java) subproject of the OpenOffice.org ODF Toolkit project. I had some experimental stuff for ODF file handling in java lying around, merged that with what lars provided as initial java sources for odf4j added some new stuff and contributed the result to odf4j. And than EIS is now using this library to provide "View as OpenDocument (Calc)" links on every HTML page in EIS where one or more tables are being shown. That means that you can request every data you can get from EIS, especially the Statistics as an OpenDocument Spreadsheet document.
Doing something like this is very easy with the things now available in odf4j. If you´ve got some database query and want to create an OpenDocument SpreadsheetDocument from the result what you basically do is:
import org.openoffice.odf.spreadsheet.SpreadsheetDocument;
import javax.swing.table.TableModel;
import javax.swing.table.DefaultTableModel;
import java.sql.ResultSet;
import java.sql.Statement;
import java.io.OutputStream;
//...
public class MyClass {
public void createDocument(OutputStream out, String uri) {
SpreadsheetDocument doc=new SpreadsheetDocument();
// do database query
// ...
// create table model
TableModel model=new DefaultTableModel();
// fill model with result of database query
//...
// create Spreadsheet in the SpreadsheetDocument based on the data in the model
doc.addSpreadsheet("data",model);
// the SpreadsheetDocument constructor created a document with one empty Spreadsheet
// named "Sheet1" this Spreadsheet is not needed anymore, so we delete it
doc.deleteSpreadsheet("Sheet1");
// store the document
doc.save(out,uri);
}
// ...
}
The OpenOffice.org ODF Toolkit project and it´s odf4j subproject have just been started some time ago and are still seeking for people helping the effort.
You can checkout odf4j from OpenOffice.org CVS via:
cvs -d:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co odftoolkit/odf4j
So far besides the stuff just mentioned for Spreadsheet Documents there´s not much specific functionality for document manipulation and information in there yet, but the basic stuff for working with the OpenDocument Package file format is there and we also have helper stuff for general XML manipulation (eg. XSL Transformation or working with org.w3c.dom trees) of ODF content etc. As demonstrated with the new EIS feature there are already use cases for where what we now have can be used in productive environment, altough it´s just all pretty alpha ;-). So well maybe you like what we´ve started and probably you would like to join the effort and might for example like to contribute some cool new methods for the SpreadsheetDocument class, it´s base class OpenDocument or for the other classes derived from the OpenDocument base class for other document types like Text Documents or Presentations.
tags: eis odf odf4j opendocument