Re: required/DEV300 CWS sb118 : cwscheckapi replaced with subsequenttests

Hi there!

[email protected] wrote:
> [... snip ....]
> @Bernd:  Note that this will render the CWSCheckAPI entries on a CWS
> EIS page meaningless.  Unlike cwscheckapi, subsequenttests does not
> report any status to EIS.
> 

I can mark the CWSCheckAPITest as unavailable in the EIS Database so it 
will only be shown on those CWS where a status has actually been 
reported in the past. I think I should do this.

May I ask why subsequenttests does not report it´s status to EIS? Is 
this a political or technical issue? Or is it just a currently missing 
feature which is planned to be added?

If it´s just lack of information on how you could transfer the status to 
EIS you could find the neccessary documentation in the wiki.

http://so-wiki.germany.sun.com/wiki/index.php/EISCwsTestResultAPI

There is a SOAP interface and a commandlinetool which you could call 
from makefiles available.

If it is a new feature we might give it also a new name when it reports 
the status to EIS.

> [...snip...]

Kind regards,
Bernd Eilers