send your bugs to desert
Download
Short Manual
Forum
Support
Desert Team
 |
 |
Desert is a client for the Borland Quality Center (BQC). Borland has established the BQC to give his users the possibility to report discovered bugs and to get informed about known bugs.
Borland has published a SOAP interface for BQC BQC to give the opportunity to develop Clients for it. Desert is a ein Java™ Frontend for this interface.
Why BQC - Desert?
Desert offers as a Java-Webstart™ application advantages of a server based application (use up-to-date versions at any time without any expense of installation, platform independent), as well as advantages of a classic gui application.
Working intensive with Borland products like Delphi™, Kylix™, JBuilder™, C++Builder™ oder VisiBroker™ you will always get situations in which you do not know if a "curios" bug in your own application is actually your own mistake or if it is a bug by the IDE. In this case it is of big advantage to be able to search through a manufacturers bug database as easy and quick as possible.
It occurs again and again ,though a bit more seldom, that you find real bug in these products. They should be transmitted and tracked as easy and transparent as possible. Borland has disclosed BQC for this purpose. Desert wants to help to make these requirements even easier for the developer.
Top of Page
Why we have developed Desert
When Marcin tried to port the Open-Source project XMLWorks from Delphi™ to Kylix™ he noticed a strange bug. Anything worked at the first go and as easy as planned, but as the unit test quickly showed the support for multidimensional variant arrays did not. The reason could not be found in the code of XMLWorks.
During the analyses he found out that the windows API is used directly for variants by Delphi. For Kylix™ Borland had to reimplement this. And in fact, the bug in XMLWorks4Kylix's variant support had it's root in a bug in the implementation of the multidimensional variant arrays in Kylix™.
On our first attempt we were disappointed while searching for error lists on the Borland website or similar because we could not find any lists or contact Person.
Then we tried to report the bug by telephone, but Borland staff rejected the error with a threadbare argumentation.
Badly disappointed we decided to try a last attempt in the Borland Newsgroups. Here we finally came across the BQC, which was exactly developed for the purposes we wanted. And: The bug was known and we could contribute towards the bug specification.
Unfortunately only a Windows Client und a Web-Application for the BQC existed. The web application had a limited functionality (e.g. no attachments could be uploaded, editing of reports was not possible, searching was limited etc.). The Windows™ client (naturely) worked only with Windows™, was obviously a problem for Kylix™ developers.
Offhand we decided to develop a Java™ client to close this gap.
Now we have the first publication of this client as BQC-Desert pre Alpha.
Top of Page
Download | Short Manual | Forum | Support | Desert Team