Difference between revisions of "OC5:FeatureTest-Support WebFinger Discovery"

From OSIS Open Source Identity Systems
Jump to: navigation, search
(Add instructions)
 
m (moved OC5:FeatureTest-Enables Discovery to OC5:FeatureTest-Support WebFinger Discovery: Enables Discovery -> Support WebFinger Discovery)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{FeatureTest
 
{{FeatureTest
   |name              = Enables Discovery
+
   |name              = Support WebFinger Discovery
 
   |testtype          = normal
 
   |testtype          = normal
 
   |identifier        = FTR-op-discovery
 
   |identifier        = FTR-op-discovery
 
   |areatested        =  
 
   |areatested        =  
 
   |status            = active
 
   |status            = active
   |summary            = Exchange in which Client Discovers and Uses OP Information
+
   |summary            = Exchange in which RP discovers user's OP location with WebFinger
 
   |testedrole        = OP
 
   |testedrole        = OP
 
   |referencesolution1 =  
 
   |referencesolution1 =  
Line 12: Line 12:
 
   |failure            = Fails
 
   |failure            = Fails
 
}}
 
}}
# Run the automated OP testing tools either using the online OP test site at http://openidtest.uninett.no/connect-provider or by downloading and running the OP testing scripts at http://www.kodtest.se/oictest/.
+
# Run the automated OP testing tools either using the online OP test site at http://openidtest.uninett.no/test#!/connect or by downloading and running the OP testing scripts at http://www.kodtest.se/oictest/.
 
## Instructions on getting started with OP testing can be found at http://openidtest.uninett.no/connect-gettingstarted.
 
## Instructions on getting started with OP testing can be found at http://openidtest.uninett.no/connect-gettingstarted.
 
# Open the result page for your solution and this test.
 
# Open the result page for your solution and this test.

Latest revision as of 16:55, 4 June 2014

{{#vardefine:page|{{#if:{{#var:page}}|{{#var:page}}|FeatureTest-Support WebFinger Discovery}}}}{{#vardefine:nr|{{#if:{{#var:nr}}|{{#expr:{{#var:nr}}+1}}|1}}}}{{#vardefine:url|{{#replace:{{#var:page}}| |_}}}}{{#if:Support WebFinger Discovery|{{#if:{{#var:DtArticleSortKey}}||}}}}{{#ifeq:{{#var:header}}|no||

{{#ifeq:no|no||
{{#if:{{#var:refs}}|[[{{#var:page}}|no_ref's]]|[[Special:Call/DT Article show Refs,page={{#var:page}},refs=yes|ref's]]}}}} {{#if:{{#var:DtArticleSortKey}}|({{#var:DtArticleSortKey}})}}    list help  [[Special:Call/DT Article copy,cat=FeatureTest,from={{#var:page}},namespace=OC5|copy]]  [[Special:Call/DT Articles list XML,type=FeatureTest,title={{#var:page}},namespace=OC5|as XML]]  edit
}}
{{#if:|Feature Test |Feature Test }}   Support WebFinger Discovery
Test Type   bgcolor={{{color}}}}}|normal
Identifier   bgcolor={{{color}}}}}|FTR-op-discovery  
Description   bgcolor={{{color}}}}}|Exchange in which RP discovers user's OP location with WebFinger  
Role tested   bgcolor={{{color}}}}}|OP  
Known Successful Reference Solution(s)   bgcolor={{{color}}}}}|{{ #if: |
[[OC5:]]}}{{ #if: |
[[OC5:]]}} {{ #if: |
}} {{ #if: |
}}  
Success Criteria   bgcolor={{{color}}}}}|Works  
Failure Criteria   bgcolor={{{color}}}}}|Fails  

Features Proven

{{#dpl:debug=1

 |resultsheader=\n
 |noresultsheader= {|\n|bgcolor=#eeeeee|No matching Feature found.\n|}\n
 |category=Feature
 |namespace=OC5
 |linksto=OC5:FeatureTest-Support WebFinger Discovery
 |nottitlematch = Feature.edit
 |include={Feature}.viewfromtest
 |includematch=/FeatureTest-Support WebFinger Discovery/s
 |table=class=sortable,-,Feature,feature_type,solution_role

}}

Instructions

  1. Run the automated OP testing tools either using the online OP test site at http://openidtest.uninett.no/test#!/connect or by downloading and running the OP testing scripts at http://www.kodtest.se/oictest/.
    1. Instructions on getting started with OP testing can be found at http://openidtest.uninett.no/connect-gettingstarted.
  2. Open the result page for your solution and this test.
  3. Record the outcome from the test "(oic-discovery)Provider configuration discovery" in the results page:
    1. If the success criteria was met, set the outcome to "Works".
    2. If the test failed, set the outcome to "Failed" and enter information about the failure in the Notes section.
    3. If other issues occurred set the result to "Issues" and describe them in the Notes section.
  4. Add either four tilde ~~~~ signs or a text name into the "Tested by" parameter.
  5. Update the Date Tested, Browser, and Operating System lines of the results page.