Difference between revisions of "I4:FeatureTest-Browser Add-On Verifies that Frame Domain and Scheme Match Root Frame"

From OSIS Open Source Identity Systems
Jump to: navigation, search
(FeatureTest-Browser Add-On Verifies that Frame Domain and Scheme Match Root Frame)
 
(Use standard status reporting conventions)
 
Line 12: Line 12:
 
   |failure            = In the cases where the frame and root domains or schemes do not match, the selector is still invoked
 
   |failure            = In the cases where the frame and root domains or schemes do not match, the selector is still invoked
 
}}
 
}}
# Open the result page for your solution and for this test
+
# Open the result page for the solution for this test.
 
# Visit http://relyingparty.federatedidentity.net/RelyingParty/framepage.aspx
 
# Visit http://relyingparty.federatedidentity.net/RelyingParty/framepage.aspx
 
# Verify that the selector activates in the first case (where the frame domain and scheme match) and is not activated in the second and third cases (where the scheme and domain do not match, respectively)
 
# Verify that the selector activates in the first case (where the frame domain and scheme match) and is not activated in the second and third cases (where the scheme and domain do not match, respectively)

Latest revision as of 20:15, 31 August 2008

{{#vardefine:page|{{#if:{{#var:page}}|{{#var:page}}|FeatureTest-Browser Add-On Verifies that Frame Domain and Scheme Match Root Frame}}}}{{#vardefine:nr|{{#if:{{#var:nr}}|{{#expr:{{#var:nr}}+1}}|1}}}}{{#vardefine:url|{{#replace:{{#var:page}}| |_}}}}{{#if:Browser Add-On Verifies that Frame Domain and Scheme Match Root Frame|{{#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=I4|copy]]  [[Special:Call/DT Articles list XML,type=FeatureTest,title={{#var:page}},namespace=I4|as XML]]  edit
}}
{{#if:|Feature Test |Feature Test }}   Browser Add-On Verifies that Frame Domain and Scheme Match Root Frame
Test Type   bgcolor={{{color}}}}}|Selector Invocation
Identifier   bgcolor={{{color}}}}}|FTR-iba-rptrigger-11  
Description   bgcolor={{{color}}}}}|In the case where the Selector trigger object is embedded in an iFrame, the frame content must be from same domain and use the same scheme as the root frame, as per ISIP Web Guide § 4.5  
Role tested   bgcolor={{{color}}}}}|Information Card Browser Add-On  
Known Successful Reference Solution(s)   bgcolor={{{color}}}}}|{{ #if: MS IE7 icardie.dll |
I4:MS IE7 icardie.dll}}{{ #if: |
[[I4:]]}} {{ #if: |
}} {{ #if: |
}}  
Success Criteria   bgcolor={{{color}}}}}|In the cases where the frame and root domains or schemes do not match, the selector is not invoked  
Failure Criteria   bgcolor={{{color}}}}}|In the cases where the frame and root domains or schemes do not match, the selector is still invoked  

Features Proven

{{#dpl:debug=1

 |resultsheader=\n
 |noresultsheader= {|\n|bgcolor=#eeeeee|No matching Feature found.\n|}\n
 |category=Feature
 |namespace=I4
 |linksto=I4:FeatureTest-Browser Add-On Verifies that Frame Domain and Scheme Match Root Frame
 |nottitlematch = Feature.edit
 |include={Feature}.viewfromtest
 |includematch=/FeatureTest-Browser Add-On Verifies that Frame Domain and Scheme Match Root Frame/s
 |table=class=sortable,-,Feature,feature_type,solution_role

}}

Instructions

  1. Open the result page for the solution for this test.
  2. Visit http://relyingparty.federatedidentity.net/RelyingParty/framepage.aspx
  3. Verify that the selector activates in the first case (where the frame domain and scheme match) and is not activated in the second and third cases (where the scheme and domain do not match, respectively)
  4. Set outcome:
    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.
  5. Add either four tilde ~~~~ signs or a text name into the "Tested by" parameter.
  6. Update the Date Tested, Browser, and Operating System lines of the results page.