| <?xml version="1.0" encoding="utf-8" ?> |
| <?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?> |
| <html> |
| <head> |
| <meta name="root" content="../../../../../" /> |
| <title>wtp milestone 4 test plan</title> |
| </head> |
| <body> |
| <h1> |
| WSDL M4 Editor test plan</h1> |
| <h2> |
| Status of this Document</h2> |
| <p> |
| This is the test plan for the WSDL Editor for the Milestone 4 release. Last updated |
| on 04/15/2005. |
| </p> |
| <h2> |
| Tests</h2> |
| <p> |
| <b>New WSDL Wizard</b> |
| <ul> |
| <li>Try the various options available on the New WSDL file options page |
| <ul> |
| <li>option to create WSDL Skeleton</li> |
| <li>SOAP...document literal, rpc literal, rpc encoded</li> |
| <li>HTTP...HTTP GET, HTTP POST</li> |
| </ul> |
| </li> |
| </ul> |
| <b>Graph View</b> |
| <ul> |
| <li>Top Level View |
| <ul> |
| <li>Actions to add/remove/rename components</li> |
| <li>Open Schema/WSDL Imports</li> |
| <li>Imported WSDL components should appear but not be editable</li> |
| <li>Inline Schemas located in the 'top level' view should allow drill down</li> |
| <li>Connecting lines should appear to show WSDL component relationships </li> |
| </ul> |
| </li> |
| <li>In Drilled Down View of Schema Components... |
| <ul> |
| <li>Test that menus show proper content for different objects</li> |
| <li>Test Drag and Drop</li> |
| <li>Ensure deleting the 'top level' component pops you back to the top view</li> |
| <li>Test selection of 'simple type' icon within an element declaration</li> |
| <li>Content that originates via derivation should be demarked with dotted box </li> |
| </ul> |
| </li> |
| </ul> |
| <b>Outline View</b> |
| <ul> |
| <li>Selection from Outline view should select the corresponding object in the graph |
| view </li> |
| <li>Context menu for a particular component should be the same in both the Graph and |
| Outline views </li> |
| </ul> |
| <b>Source View</b> |
| <ul> |
| <li>Test editing features |
| <ul> |
| <li>Add WSDL Components</li> |
| <li>Delete from source</li> |
| <li>Copy and paste</li> |
| <li>Test for invalid content </li> |
| </ul> |
| </li> |
| <li>Test 'standard' xml content assist support (see xml source editor) for adding WSDL |
| and schema elements</li> |
| </ul> |
| <b>Properties View</b> |
| <ul> |
| <li>Properties view should be available for all selected schema components</li> |
| <li>Test that view can't be 'broken'... should always have 'good' content</li> |
| <li>Imported WSDL components should not be editable through the properties</li> |
| <li>Renaming components should 'auto refactor' within source file (references to renamed |
| component should be updated)</li> |
| <li>Update documentation for various components </li> |
| </ul> |
| <b>Set Existing Component Dialog</b> |
| <ul> |
| <li>Set Existing Component Dialog launched via the context menu or properties |
| <ul> |
| <li>Port</li> |
| <li>Binding</li> |
| <li>Input</li> |
| <li>Output</li> |
| <li>Fault</li> |
| <li>Part</li></ul> |
| </li> |
| <li>Adjust the search scope. The available components displayed should be updated</li> |
| <li>The text filter located at the top of the dialog is used to filter the available |
| types </li> |
| </ul> |
| <b>Generate Binding Content</b> |
| <ul> |
| <li>Click on a Binding and select "Generate Binding Content..." from the context menu. |
| Select the "Overwrite existing binding information option". Ensure the proper binding |
| information is generated</li> |
| <li>Test out the different Binding options (SOAP, HTTP, etc...) </li> |
| </ul> |
| <b>Smart Renaming</b> |
| <ul> |
| <li>Test smart renaming on the following Components |
| <ul> |
| <li> |
| Operation</li> |
| <li> |
| Fault</li> |
| <li> |
| Message</li> |
| <li>Part</li></ul> |
| </li> |
| <li>Renaming one of the above elements should also rename it's 'children' if the 'child' |
| has a generated name. For example, "MyOperationName" (Operation) --> Input --> "MyOperationNameRequest" |
| (Message) --> "MyOperationNameRequest" (Part) A rename on Operation to "NewOp" will |
| cause the following result: "newOpName" (Operation) --> Input --> "newOpNameRequest" |
| (Message) --> "newOpNameRequest" (Part)</li> |
| <li>The same pattern follows when renaming a Fault, Message, and Part</li> |
| <li>Initiate renaming via the context menu or the properties view </li> |
| </ul> |
| <b>General</b> |
| <ul> |
| <li>Test the various menu actions available for different components</li> |
| <li>Reload dependancies action from the WSDL Editor menu bar</li> |
| <li>Test 'Edit Namespaces...' action</li> |
| <li>Add 'import'' and test that 'new' components are available in the 'set type' dialog</li> |
| <li>Menu actions for 'categories' should only provide actions appicable to that particular |
| category (e.g. element category should have 'Add Element')</li> |
| <li>Undo/Redo</li> |
| <li>View selection synchronization</li> |
| <li>Editing synchronization : source -> model (perform source changes below and |
| ensure model is intact)</li> |
| <ul> |
| <li>cut and paste sections to/from source view</li> |
| <li>make various random changes in the souce view and then undo</li> |
| <li>delete and restore component declarations from source and ensure references are |
| updated</li> |
| <li>change a file locally and refresh </li> |
| </ul> |
| <li>Editing synchronization : model -> source (perform graphical changes below and |
| ensure source is intact)</li> |
| <ul> |
| <li>make random changes to the WSDL model via the graphical views</li> |
| <li>make various changes in the souce view and then undo </li> |
| </ul> |
| <li>F3 support |
| <ul> |
| <li>F3 on component references should cause selection to 'jump' to referenced component</li> |
| <li>F3 on imports should open the imported schema or WSDL </li> |
| </ul> |
| </li> |
| </ul> |
| </p> |
| </body> |
| </html> |
