Difference between revisions of "I4:FeatureTest-Selector Preserves Not-Understood Elements from .crd File"
From OSIS Open Source Identity Systems
Mike.Jones (Talk | contribs) (FeatureTest-Selector Preserves Not-Understood Elements from .crd File) |
Mike.Jones (Talk | contribs) (Remove reference solution) |
||
| Line 7: | Line 7: | ||
|summary = Tests that selector preserves not-understood XML elements from .crd files, including them when the cards containing them are exported | |summary = Tests that selector preserves not-understood XML elements from .crd files, including them when the cards containing them are exported | ||
|testedrole = Information Card Identity Selector | |testedrole = Information Card Identity Selector | ||
| − | |referencesolution1 = | + | |referencesolution1 = |
|referencesolution2 = | |referencesolution2 = | ||
|success = The card is succefully created and works | |success = The card is succefully created and works | ||
| Line 13: | Line 13: | ||
}} | }} | ||
# Open the result page for your solution and for this test. | # Open the result page for your solution and for this test. | ||
| − | # Import the card | + | # Import the card https://ipsts.federatedidentity.net/MgmtConsole/UnknownElementCard.crd into the selector. |
# Export the "UnknownElement" card to a .crds file. | # Export the "UnknownElement" card to a .crds file. | ||
# View the decrypted contents of the .crds file using the tool at http://xmldap.org/sts/decrypt . | # View the decrypted contents of the .crds file using the tool at http://xmldap.org/sts/decrypt . | ||
Latest revision as of 15:38, 1 October 2008
{{#vardefine:page|{{#if:{{#var:page}}|{{#var:page}}|FeatureTest-Selector Preserves Not-Understood Elements from .crd File}}}}{{#vardefine:nr|{{#if:{{#var:nr}}|{{#expr:{{#var:nr}}+1}}|1}}}}{{#vardefine:url|{{#replace:{{#var:page}}| |_}}}}{{#if:Selector Preserves Not-Understood Elements from .crd File|{{#if:{{#var:DtArticleSortKey}}||}}}}{{#ifeq:{{#var:header}}|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 }} | Selector Preserves Not-Understood Elements from .crd File |
| Test Type | bgcolor={{{color}}}}}|Card Usage |
| Identifier | bgcolor={{{color}}}}}|FTR-iis-cardmgmt-11 |
| Description | bgcolor={{{color}}}}}|Tests that selector preserves not-understood XML elements from .crd files, including them when the cards containing them are exported |
| Role tested | bgcolor={{{color}}}}}|Information Card Identity Selector |
| Known Successful Reference Solution(s) | bgcolor={{{color}}}}}|{{ #if: | [[I4:]]}}{{ #if: | [[I4:]]}} {{ #if: | }} {{ #if: | }} |
| Success Criteria | bgcolor={{{color}}}}}|The card is succefully created and works |
| Failure Criteria | bgcolor={{{color}}}}}|Not-understood elements cause the card creation to fail |
Features Proven
{{#dpl:debug=1
|resultsheader=\n
|noresultsheader= {|\n|bgcolor=#eeeeee|No matching Feature found.\n|}\n
|category=Feature
|namespace=I4
|linksto=I4:FeatureTest-Selector Preserves Not-Understood Elements from .crd File
|nottitlematch = Feature.edit
|include={Feature}.viewfromtest
|includematch=/FeatureTest-Selector Preserves Not-Understood Elements from .crd File/s
|table=class=sortable,-,Feature,feature_type,solution_role
}}
Instructions
- Open the result page for your solution and for this test.
- Import the card https://ipsts.federatedidentity.net/MgmtConsole/UnknownElementCard.crd into the selector.
- Export the "UnknownElement" card to a .crds file.
- View the decrypted contents of the .crds file using the tool at http://xmldap.org/sts/decrypt .
- Verify that this XML element is present in the .crds file: <unknownElement xmlns="http://unknown"><donNotknowThisOneEither /><norThis /></unknownElement>
- Set outcome:
- If the success criteria was met, set the outcome to "Works".
- If the test failed, set the outcome to "Failed" and enter information about the failure in the Notes section.
- If other issues occurred set the result to "Issues" and describe them in the Notes section.
- Add either four tilde ~~~~ signs or a text name into the "Tested by" parameter.
- Update the Date Tested, Browser, and Operating System lines of the results page.
