incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Story (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLEREZZA-479) WebID test suite
Date Tue, 10 May 2011 13:52:47 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031194#comment-13031194
] 

Henry Story commented on CLEREZZA-479:
--------------------------------------

Btw, this is only one part of the needed test suite. The other part that is also needed by
the W3C WebID Incubator group,  and of course that would have helped identify the bug Reto
just found, is the creation of a client tester to test the endpoint. It would for example
be able to create a certificate with a webid that has not associated Profile, and see if it
can still login.

Such a test suite can then be deployed against all webid enabled servers in order to build
a profile of the capabilities of each.

> WebID test suite
> ----------------
>
>                 Key: CLEREZZA-479
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-479
>             Project: Clerezza
>          Issue Type: New Feature
>            Reporter: Henry Story
>
> We need a test suite to be able to help work out where WebID authentication fails. This
can be useful in a number of ways:
>    1. for helping developers and end users work out where a problem lies
>    2. to build test suites to test the local webid implementations. 
> For 2 the result should be marked up so as to show what tests succeeded and where the
error occurred using an ontology to be specified on the w3c webid working group. This will
then allow other robot services to be created which can the send requests, broken or valid,
and check if the results are correct. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message