You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Henry Story (JIRA)" <ji...@apache.org> on 2011/03/28 19:38:05 UTC
[jira] [Created] (CLEREZZA-479) WebID test suite
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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033017#comment-13033017 ]
Reto Bachmann-Gmür commented on CLEREZZA-479:
---------------------------------------------
sorry my comment was intended for CLEREZZA-473.
> WebID test suite
> ----------------
>
> Key: CLEREZZA-479
> URL: https://issues.apache.org/jira/browse/CLEREZZA-479
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
> Assignee: 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
[jira] [Resolved] (CLEREZZA-479) WebID test suite
Posted by "Henry Story (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henry Story resolved CLEREZZA-479.
----------------------------------
Resolution: Fixed
The test suite works. It could certainly be made more beautiful, and there are a large number of enhancements that could be made. But those can be new issues. Perhaps sub issues of this one?
> WebID test suite
> ----------------
>
> Key: CLEREZZA-479
> URL: https://issues.apache.org/jira/browse/CLEREZZA-479
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
> Assignee: 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032988#comment-13032988 ]
Reto Bachmann-Gmür commented on CLEREZZA-479:
---------------------------------------------
@Henry: as issues CLEREZZA-509 depends on this one (by mofifying classes added with this issue you should close this issue. As long as this isn't closed dependent issues should not be resolved.
> WebID test suite
> ----------------
>
> Key: CLEREZZA-479
> URL: https://issues.apache.org/jira/browse/CLEREZZA-479
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
> Assignee: 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
[jira] [Updated] (CLEREZZA-479) WebID test suite
Posted by "Tommaso Teofili (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tommaso Teofili updated CLEREZZA-479:
-------------------------------------
Fix Version/s: 0.2-incubating
> WebID test suite
> ----------------
>
> Key: CLEREZZA-479
> URL: https://issues.apache.org/jira/browse/CLEREZZA-479
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
> Assignee: Henry Story
> Fix For: 0.2-incubating
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Henry Story (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031185#comment-13031185 ]
Henry Story commented on CLEREZZA-479:
--------------------------------------
How can a test suite create a problem. Sorry no rollback. Will first test, then fix.
> 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Henry Story (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031385#comment-13031385 ]
Henry Story commented on CLEREZZA-479:
--------------------------------------
Commit 1101645 fixes the security issue
http://svn.apache.org/viewvc?view=rev&rev=1101645
> 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Henry Story (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029544#comment-13029544 ]
Henry Story commented on CLEREZZA-479:
--------------------------------------
WebId is a cross platform authentication protocol. People who login to clerezza with a WebId should be able to login to any other WebID compliant system too. Since not
everybody is going to be using Clerezza, initially at least, we should help the others built test suites that produce the same output as this one, so that server
testers can be deployed to test the functionality of any clerezza instance and build comparative reports for them. And of course if someone else writes a better
WebId implementation than this one according to these tests then it will help admins make informed choices.
As a result the tests that can be used for the WebID tests in clerezza should later also be good to test any other WebId implementation.
Also building distributed test suites could be very useful, so that no instance can put out predetermined results for the testing agents.
Henry
Social Web Architect
http://bblfish.net/
> 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Henry Story (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032996#comment-13032996 ]
Henry Story commented on CLEREZZA-479:
--------------------------------------
CLEREZZA-509 "enable pingback protocol" has nothing to do with the WebID test suite.
> WebID test suite
> ----------------
>
> Key: CLEREZZA-479
> URL: https://issues.apache.org/jira/browse/CLEREZZA-479
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
> Assignee: 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
[jira] [Assigned] (CLEREZZA-479) WebID test suite
Posted by "Henry Story (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henry Story reassigned CLEREZZA-479:
------------------------------------
Assignee: Henry Story
> WebID test suite
> ----------------
>
> Key: CLEREZZA-479
> URL: https://issues.apache.org/jira/browse/CLEREZZA-479
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
> Assignee: 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Henry Story (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (CLEREZZA-479) WebID test suite
Posted by "Henry Story (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henry Story resolved CLEREZZA-479.
----------------------------------
Resolution: Fixed
documentation added and easy startup done. Please open new issues for improvements.
> WebID test suite
> ----------------
>
> Key: CLEREZZA-479
> URL: https://issues.apache.org/jira/browse/CLEREZZA-479
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
> Assignee: 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
[jira] [Reopened] (CLEREZZA-479) WebID test suite
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reto Bachmann-Gmür reopened CLEREZZA-479:
-----------------------------------------
Reopening the issue, because of:
- lack of documentation: for a testsuite to be of use it needs some sort of documentation
- even with some support on the mailing list didn't get it to run, cryptic message on /test/webID
> WebID test suite
> ----------------
>
> Key: CLEREZZA-479
> URL: https://issues.apache.org/jira/browse/CLEREZZA-479
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
> Assignee: 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031180#comment-13031180 ]
Reto Bachmann-Gmür commented on CLEREZZA-479:
---------------------------------------------
There seems to be a major security issue here: if the webid cannot be dereference a new user can still log in and rights can be granted to this user, anybody can now login and claim this webid and impersonate that user, no certificate validation occurs. Please roll back this changes asap.
> 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Henry Story (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015827#comment-13015827 ]
Henry Story commented on CLEREZZA-479:
--------------------------------------
Hasan, I suppose it depends what quality you are expecting the whole release to have.
The test endpoint for foafssl is being built to allow it to be tested against a standard process that the WebID incubator group is going to put together.
Reto's test failure is now a MailManPermission problem.
Henry
> 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034898#comment-13034898 ]
Reto Bachmann-Gmür commented on CLEREZZA-479:
---------------------------------------------
WebIDClaim that was added for this issue contains several public members that are missing scaladoc comments, the class comment should explain difference to the X509CLaim class. Similar issues with X509Claim object and class.
> WebID test suite
> ----------------
>
> Key: CLEREZZA-479
> URL: https://issues.apache.org/jira/browse/CLEREZZA-479
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
> Assignee: 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015311#comment-13015311 ]
Reto Bachmann-Gmür commented on CLEREZZA-479:
---------------------------------------------
It seems the changes to the UserUtil cause some tests to fail:
$ cat platform.mail/target/surefire-reports/org.apache.clerezza.platform.mail.MailManPermissionTest.txt
-------------------------------------------------------------------------------
Test set: org.apache.clerezza.platform.mail.MailManPermissionTest
-------------------------------------------------------------------------------
Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.065 sec <<< FAILURE!
testImpliesSelf(org.apache.clerezza.platform.mail.MailManPermissionTest) Time elapsed: 0.042 sec <<< ERROR!
java.lang.NullPointerException
at org.apache.clerezza.platform.security.UserUtil.getUserName(UserUtil.java:68)
at org.apache.clerezza.platform.security.UserUtil.getCurrentUserName(UserUtil.java:45)
at org.apache.clerezza.platform.mail.MailManPermission.patternImplies(MailManPermission.java:81)
at org.apache.clerezza.platform.mail.MailManPermission.implies(MailManPermission.java:55)
at org.apache.clerezza.platform.mail.MailManPermissionTest.testImpliesSelf(MailManPermissionTest.java:68)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59)
at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98)
at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79)
at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87)
at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77)
at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42)
at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88)
at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51)
at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44)
at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> 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
[jira] [Commented] (CLEREZZA-479) WebID test suite
Posted by "Hasan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015805#comment-13015805 ]
Hasan commented on CLEREZZA-479:
--------------------------------
I assume platform.security.foafssl is not ready yet for release, therefore I'll change its state to INPROGRESS in CLEREZZA-485
> 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