OC5:FeatureTest-Can Make Request with code Response Type

From OSIS Open Source Identity Systems
Jump to: navigation, search

{{#vardefine:page|{{#if:{{#var:page}}|{{#var:page}}|FeatureTest-Can Make Request with code Response Type}}}}{{#vardefine:nr|{{#if:{{#var:nr}}|{{#expr:{{#var:nr}}+1}}|1}}}}{{#vardefine:url|{{#replace:{{#var:page}}| |_}}}}{{#if:Can Make Request with code Response Type|{{#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 }}   Can Make Request with code Response Type
Test Type   bgcolor={{{color}}}}}|normal
Identifier   bgcolor={{{color}}}}}|FTR-rp-rtyp-code  
Description   bgcolor={{{color}}}}}|Make a request using response_type=code  
Role tested   bgcolor={{{color}}}}}|RP  
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-Can Make Request with code Response Type
 |nottitlematch = Feature.edit
 |include={Feature}.viewfromtest
 |includematch=/FeatureTest-Can Make Request with code Response Type/s
 |table=class=sortable,-,Feature,feature_type,solution_role

}}

Instructions

  1. Open the result page for your solution and this test.
  2. WHAT TO DO TBD
  3. Set outcome 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.