You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org> on 2011/05/05 21:17:03 UTC

[jira] [Commented] (CLEREZZA-479) WebID test suite

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

Reto Bachmann-Gmür commented on CLEREZZA-479:
---------------------------------------------

I think the WebID Test suite should be a separate bundle, the normal authentication module (platform.security.foafssl) should of course provide reasonable error messages to allow debugging, but a "test suites to test the local webid implementations" seems like something that isn't needed on a regularly deployed clerezza instance. Also I don't understand the plural of webidimplementations, I don't see how and why a colerezza instance could have multiple webid implementations.

> 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