Halo Andre:
I appologize for my "contextfree" answer - its no question that I
appreciate your help.
"I meant the testtool interpreter of course" - that was meant as a
remark to your mail:
/The problem with VB(A) is, that this is available on WIndows only./
and re "what Thorsten said" - from his mail yesterday -:
/My suggestion is still to get a portal inside OOo, where all TestTool
results are collected. ... If you run a test with 20 errors and 50
warnings,
does not say anything. *Because all tests should run without any error*!
..../ (bold smo)
...And as I often wrote, the resources in Sun QA are very limited. ...
I am sorry to burn the bandwidth. Ill do two extra testtool tests as a
penitence (g).
Vito
Andre Schnabel wrote:
Hi Vito,
Vito Smolej schrieb:
I meant the testtool interpreter of course. But for me the question
is closed. Thorsten said all (one more - last for me - time).
sorry to say that .. but this is once again a Mail, where I cannot see
the context. Top quoting is not the only point ... that is
problematic, I cannot follow your ideas.
The initial complaint was, that you could not use the analyze scripts
on windows (because you could not use Perl) correct?
My answer was that the scripts would run perfectly if cygwin is
installed. So - no matter if developer ressources at Sun are available
or not - there is no (high priority) need to implement all those
analyze scripts within testtool.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
