Helge Delfs wrote:
Hi Shaun,
see my comments inline.
Shaun McDonald wrote:
If vcltesttoolglue has been designed using the MVC pattern then I would
recommend using JSP. This would allow for a reuse of the model code. I
have used this previously in a project. After the initial planning both
the server (web interface) and the Java application worked well together
with good code reuse between the server and client. The programming was
also simpler once you got your head around the idea of having the code
and display different.
AFAIK vcltesttoolglue is only designed to give automated testers an easy
to interpret overview and display of testtool results (offline and
local) and wasn't developed as an approach to create an interface
between a web-application and testtool. Best would be TBO states hist
tooling....I will ask him to do so.
Helge is right;
Since there is currently no public database available for test results,
the priority
to enable this in VCL TestTool Glue is very low for me. There are other
functions to do
first. And since it is only a spare time project, I won't think about it
this year...
I even didn't think in a client/server way for this function.
(Details at http://vcltesttoolglue.sourceforge.net)
But the way, how to submit results to the database, should also be
possible by the
plain VCL TestTool. I could think of several ways to get the test
results into the database,
which need some discussions and evaluation.
VCL TestTool Glue currently shows the content of the result file (.res),
which leads to some
wrong results in warnings/errors count and available error messages.
This problem is not available, if the test extract results are used,
which are currently not written by default.
(http://qa.openoffice.org/qatesttool/status_collecting.txt)
cheers
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
