Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "WSDL Test Plan"

Line 11: Line 11:
 
<table width="100%"><tr><td valign="top" bgcolor="#0080c0"><big><b><font face="Arial,Helvetica" color="#ffffff">&nbsp;&nbsp;Task Oriented Tests</font></b></big></td>
 
<table width="100%"><tr><td valign="top" bgcolor="#0080c0"><big><b><font face="Arial,Helvetica" color="#ffffff">&nbsp;&nbsp;Task Oriented Tests</font></b></big></td>
 
</tr></table>
 
</tr></table>
−
<h3>Test Case 1 : Start From Scratch</h3>
+
<h1>WSDL M4 Editor test plan</h1>
−
<ol>
+
<h2>Status of this Document</h2>
−
<li>
+
<p>This is the test plan for the WSDL Editor for the Milestone 4 release. Last updated on 05/04/2006.</p>
−
Use the New XML Schema Wizard to create a new schema (alternative) Use New File to create a blank 'xsd' file ... everything should still work
+
<h2>Task Oriented Tests</h2>
−
<br/>
+
<p>
−
</li>
+
<h3>
−
<br/>
+
<b>Test Case 1 : Start From Scratch - Standalone</b>
−
<li>Select a 'target' schema that you can attempt to reproduce. Here's some suggestions but feel free to come up with your own
+
</h3>
 +
<ol>
 +
<li>
 +
Use the New WSDL Wizard to create a new schema  
 +
<br/>(alternative) Use New File to create a blank 'wsdl' file ... everything should still work
 +
<p/>
 +
</li>
 +
<li>
 +
Select a 'target' WSDL that you can attempt to reproduce. Here's some suggestions but feel free to come up with your own
 +
<p />
 +
<ul>
 +
<table border='1'>
 +
<tr bgcolor="#CCCCCC">
 +
<td>Description</td>
 +
<td>Where</td>
 +
</tr>
 +
<tr>
 +
<td>PhoneBanking</td>
 +
<td>XML Examples Project</td>
 +
</tr>
 +
<tr>
 +
<td>Google Search API</td>
 +
<td><a href="http://api.google.com/GoogleSearch.wsdl">link</a></td>
 +
</tr>
 +
<tr>
 +
<td>Fax</td>
 +
<td><a href="http://www.sms.mio.it/webservices/sendmessages.asmx?WSDL">link</a></td>
 +
</tr>
 +
</table>
 +
</ul>
 +
<p />
 +
</li>
 +
<li>
 +
Using the target WSDL as a guide, utilize the design view to reproduce it. Attempt to use a top down flow since this best simulates how a user would go about building from scratch (e.g. start with the main elements and types and work your way down to the leaf objects.
 +
Be sure to open bugs if...
  
−
<ul>
+
<p />
−
  <table border='1'>
+
<ul>
−
    <tr bgcolor="#CCCCCC">
+
<li>you run into quirky problems that make editing feel unnatural</li>
−
      <td>Description</td>
+
<li>you need to go off to the outline or source view to work around problems</li>
−
      <td>Where</td>
+
<li>you hit performance problems that affect your productivity</li>
−
    </tr>
+
<li>etc.</li>
−
    <tr>
+
</ul>
−
      <td>GolfCourse</td>
+
<p />
−
      <td>XML Examples Project</td>  
+
</li>
−
    </tr>
+
<li>
−
    <tr>   
+
When you think your WSDL is complete, use the validator to ensure it's valid.
−
      <td>SpaceWarGame</td>
+
Since the editor was used to author the document there should be very few problems.  
−
         
+
If there are validation problems...
−
      <td>XML Examples Project</td>  
+
<p/>
−
    </tr>
+
<ul>
−
    <tr>
+
<li>look at the problems carefully and consider why the editor produced these
−
      <td>OrgChart</td>
+
    (some of the validation problems are unavoidable but in general the editor should be fairly good at protecting the users against 'bad' schemas)
−
      <td>XML Examples Project</td>  
+
</li>
−
    </tr>  
+
<li>it's likely that the user will need to use the source view to fix them</li>
−
  </table>  
+
<li>ensure that all problems can be fixed in the source view and that red squggles work (e.g.
−
</ul>
+
        as you fix things in the source view ensure that red squiggle indicators go away)</li>
−
</li>
+
<li>ensure that when you flip back to the design view that any source changes are reflected in the view</li>
−
<br/>
+
</ul>
−
<li>Using the target schema as a guide, utilize the design view to reproduce it. Attempt to use a top down flow since this best simulates how
+
<p />
−
a user would go about building from scratch (e.g. start with the main elements and types and work your way down to the leaf elements and types).
+
</li>
−
Be sure to open bugs if...
+
<li>As a final test open use the 'jst' tools to generate and deploy a skeletong web services for the WSDL
 +
</li>
 +
</ol>
  
−
<ul>
+
<h3>
−
  <li>you run into quirky problems that make editing feel unnatural</li>
+
<b>Test Case 2 : Start From Scratch - One Piece of a Larger Project</b>
−
  <li>you need to go off to the outline or source view to work around problems</li>
+
</h3>
−
  <li>you hit performance problems that affect your productivity</li>
+
<ol>
−
  <li>etc.</li>
+
<li>
−
</ul>
+
Repeat Test Case 1 but recreate a WSDL that's uses a muti-file pattern . Here's some examples...
 +
<p>
 +
<ul>
 +
<table border='1'>
 +
<tr bgcolor="#CCCCCC">
 +
<td>Name</td>
 +
<td>Where</td>
 +
</tr>
 +
<tr>
 +
<td>SpaceWarGame-b</td>
 +
<td>XML Examples Project</td>
 +
</tr>
 +
<tr>
 +
<td>PhoneBanking-b</td>
 +
<td>XML Examples Project</td>
 +
</tr>
 +
</table>
 +
</ul>
 +
</p>
 +
<p />
 +
</li>
 +
<li>Be sure to utilize the 'Browse...' function when editing type and element references.</li>
 +
<li>Inspect the schema after using 'Browse...' to ensure that the &lt;include&gt; or &lt;import&gt; and the 'xmlns:xxx' gets updated correctly.</li>
 +
<li>Inspect the source view after using 'Browse...' to ensure the type or element reference is not red squiggled (and muck with it to make sure the squiggle does show when expected)</li>
 +
</ol>
  
−
</li>
+
<h3>
−
<br/>
+
<b>Test Case 3 : Visualize and Browse a Large/Complex WSDL</b>
−
<li>When you think your schema is complete, use the validator to ensure it's valid.
+
</h3>
−
<ul>
+
<ol>
−
  <li>since the editor was used to author the schema there should be very few validation  problems (if any).  If there are some look at these carefully and consider why the editor produced these.</li>
+
<li>Select a WSDL that we want to view.</li>
−
  <li>some of the validation problems are unavoidable but in general
+
<li>
−
the editor should be fairly good at protecting the users against 'bad'
+
Use the design view to naviagate the WSDL and open referenced XML Schemas. Ensure all of the following work...
−
schemas)</li>
+
<p />
−
<li>if there are problems it's likely that the user will need to use
+
<ul>
−
the source view to fix them</li>
+
<li>click on the 'arrow' beside an element or complex type in the portType ... ensure a schema editor is opened and the 'clicked' object is shown</li>
−
<li>ensure that all problems can be fixed in the source view and that
+
<li>after following a chain of referenes, ensure the 'back arrow' button allows you to reverse back up the chain</li>
−
red squggles work</li>
+
<li>expand the binding objects to ensure they layout correctly in their 'ruler-ish' form</li>
−
<li>as you fix things in the source view ensure that red squiggle indicators
+
</ul>
−
go away</li>
+
<p />
−
<li>ensure that when you flip back to the design view that any source
+
<li>
−
view changes are reflected in the design view</li>
+
Use the source view to naviage thru the WSDLs and XSDs. Ensure all of the following work...
−
</ul>
+
<p>
−
 
+
<ul>
−
</li>
+
<li>hold down crtl to see the hyperlinks as you mouse over them, ensure hyperlins appear for all 'references'</li>
−
<br/>
+
<li>ctrl-lick or F3 on hypelinksto ensure 'open on' works</li>
−
<li>As a final test open an XML file that validates for the 'target'
+
<li>after following a chain of referenes, ensure the 'back arrow' button allows you to reverse back up the chain</li>
−
schema and edit a copy so that it point to the 'new' schema. Ensure
+
</ul>
−
the XML file validates against the 'new' schema.  If it doesn't validate
+
</p>
−
ensure the schema editor helps you fix the problems.
+
</li>
−
</li></ol>
+
<li>Navigate thru the WSDLs and XSDs using both the design and source view (flipping between 'em) and ensure both modes of navigation work together nicely.</li>
−
----
+
<li>Use the outline view in conjuction and ensure it interacts as expected with the source and design view</li>
−
 
+
<li>From the source, design and outline views. Use the 'references-&gt;project' or 'references->workspace' for several components (portTypes, bindings, types, elements etc.) to understand how components are reused.</li>
−
<h3><b>Test Case 2 : Start From Scratch - One Piece of a Larger Project</b></h3>
+
</li>
−
<ol>
+
</ol>
−
<li>Repeat Test Case 1 but recreate a schema that's a part of a multi-schema project. Here's some examples...
+
</p>
−
<ul>
+
<h2>Function Oriented Tests</h2>
−
  <table border='1'>
+
<p>
−
    <tr bgcolor="#CCCCCC">
+
<b>New WSDL Wizard</b>
−
      <td>Name</td>
+
<ul>
−
      <td>Where</td>
+
<li>
−
    </tr>
+
Try the various options available on the New WSDL file options page
−
    <tr> 
+
<ul>
−
      <td>SpaceWarGame-b</td>
+
<li>option to create WSDL Skeleton</li>
−
      <td>XML Examples Project</td>
+
<li>SOAP...document literal, rpc literal, rpc encoded</li>
−
    </tr>
+
<li>HTTP...HTTP GET, HTTP POST</li>
−
    <tr> 
+
</ul>
−
      <td>oagis-8</td>
+
</li>
−
      <td>[http://www.openapplications.org/downloads/oagidownloads.htm link]</td>
+
</ul>
−
    </tr>
+
<b>design View</b>
−
  </table>
+
<ul>
−
</ul>
+
<li>
−
</li>
+
Top Level View
−
<li>Be sure to utilize the 'Browse...' function when editing type and element references.
+
<ul>
−
</li>
+
<li>Actions to add/remove/rename components</li>
−
<li>Inspect the schema after using 'Browse...' to ensure that the &lt;include&gt;
+
<li>Open Schema/WSDL Imports</li>
−
or &lt;import&gt; and the 'xmlns:xxx' gets updated correctly.
+
<li>Imported WSDL components should appear but not be editable</li>
−
</li>
+
<li>Inline Schemas located in the 'top level' view should allow drill down</li>
−
<li>Inspect the source view after using 'Browse...' to ensure the type or element reference is not red squiggled (and muck with it to make sure
+
<li>Connecting lines should appear to show WSDL component relationships</li>
−
the squiggle does show when expected)
+
</ul>
−
</li>
+
</li>
−
</ol>
+
<li>
−
<br/>
+
In Drilled Down View of Schema Components...
−
----
+
<ul>
−
 
+
<li>Test that menus show proper content for different objects</li>
−
<h3><b>Test Case 3 : Visualize and Browse a Large Schema</b></h3>
+
<li>Test Drag and Drop</li>
−
<ol>
+
<li>Ensure deleting the 'top level' component pops you back to the top view</li>
−
<li>Select a schema that we want to view.
+
<li>Test selection of 'simple type' icon within an element declaration</li>
−
</li>
+
<li>Content that originates via derivation should be demarked with dotted box</li>
−
<br/>
+
</ul>
−
<li>Use the design view to naviagate thru the schema(s). Ensure all of the following work...
+
</li>
−
<br/>
+
</ul>
−
<ul>
+
<b>Outline View</b>
−
  <li>click on items listed in the top level view to ensure 'open on' works</li>
+
<ul>
−
  <li> double click on type headers to 'open on' works</li>
+
<li>Selection from Outline view should select the corresponding object in the design view</li>
−
  <li> after following a chain of referenes, ensure the 'back arrow' button
+
<li>Context menu for a particular component should be the same in both the design and Outline views</li>
−
allows you to reverse back up the chain</li>
+
</ul>
−
  <li>as you navigate ensure the design view displays the correct thing
+
<b>Source View</b>
−
      and the layout and line routing is correct</li>    
+
<ul>
−
</ul>
+
<li>
−
<br/>  
+
Test editing features
−
<li>Use the source view to naviage thru the schema(s). Ensure all of the following work...
+
<ul>
−
<br/>
+
<li>Add WSDL Components</li>
−
<ul>
+
<li>Delete from source</li>
−
  <li>hold down crtl to see the hyperlinks as you mouse over them, ensure
+
<li>Copy and paste</li>
−
hyperlins appear for all 'references'
+
<li>Test for invalid content</li>
−
  </li>
+
</ul>
−
  <li>ctrl-lick or F3 on hypelinksto ensure 'open on' works</li>
+
</li>
−
  <li>after following a chain of referenes, ensure the 'back arrow' button
+
<li>Test 'standard' xml content assist support (see xml source editor) for adding WSDL and schema elements</li>
−
allows you to reverse back up the chain</li>
+
</ul>
−
</ul>
+
<b>Properties View</b>
−
</li>
+
<ul>
−
<br/>
+
<li>Properties view should be available for all selected schema components</li>
−
<li>Browse the schema(s) by flipping between both the design and source
+
<li>Test that view can't be 'broken'... should always have 'good' content</li>
−
view and ensure source view and design view navigation work together nicely.
+
<li>Imported WSDL components should not be editable through the properties</li>
−
</li>
+
<li>Renaming components should 'auto refactor' within source file (references to renamed component should be updated)</li>
−
<br/>
+
<li>Update documentation for various components</li>
−
<li>Use the outline view in conjuction with the source and design view.
+
</ul>
−
</li>
+
<b>Set Existing Component Dialog</b>
−
<br/>
+
<ul>
−
<li>From the source, design and outline views. Use the 'references-&gt;project'
+
<li>
−
or 'references->workspace' for several components (types, elements etc.)
+
Set Existing Component Dialog launched via the context menu or properties
−
to understand how components are reused in the schema(s).
+
<ul>
−
</li>
+
<li>Port</li>
−
</li>
+
<li>Binding</li>
−
</ol>
+
<li>Input</li>
−
----
+
<li>Output</li>
−
<h3><b>Test Case 4 : Refactor a large schema project</b></h3>
+
<li>Fault</li>
−
<ol>
+
<li>Part</li>
−
<li>a) Select one of the existing refactoring 'before and after' projects form the list below
+
</ul>
−
<br/>-- or ---
+
</li>
−
<br/>b) Use any project and come up with a reorganization 'plan' (change
+
<li>Adjust the search scope. The available components displayed should be updated</li>
−
names, move things around etc.) that will describe your 'target' project.
+
<li>The text filter located at the top of the dialog is used to filter the available types</li>
−
</li>
+
</ul>
−
<li>Use the editor's editing and refactoring support to make the existing
+
<b>Generate Binding Content</b>
−
project look like the 'target' project.
+
<ul>
−
</li>
+
<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>After each refactoring is applied ensure that the project validates.
+
<li>Test out the different Binding options (SOAP, HTTP, etc...)</li>
−
</li>
+
</ul>
−
</ol>
+
<b>Smart Renaming</b>
−
__NOTOC__
+
<ul>
−
 
+
<li>
−
<table width="100%"><tr><td valign="top" bgcolor="#0080c0"><big><b><font face="Arial,Helvetica" color="#ffffff">&nbsp;&nbsp;Function Oriented Tests</font></b></big></td>
+
Test smart renaming on the following Components
−
</tr></table>
+
<ul>
−
 
+
<li>Operation</li>
−
<h3><b>Actions Tests</b></h3>
+
<li>Fault</li>
−
 
+
<li>Message</li>
−
<ol>
+
<li>Part</li>
−
<li> from top level view test <b>Add</b>ing each kind of component </li>
+
</ul>
−
<li> from an element test the <b>Set Type</b> action </li>
+
</li>
−
<li> from a complex type test <b>Add</b>ing an element, attribute, sequence and choice</li>
+
<li>
−
<li> from various contexts test the <b>Delete</b> action </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
−
<li> show properties</li>
+
the following result: "newOpName" (Operation) --> Input --> "newOpNameRequest" (Message) --> "newOpNameRequest" (Part)
−
<li> set type / set element / set element ref</li>
+
</li>
−
<li> set multiplicity</li>
+
<li>The same pattern follows when renaming a Fault, Message, and Part</li>
−
<li> from the schema test the <b>Edit Namespaces...</b> action (from properties)</li>
+
<li>Initiate renaming via the context menu or the properties view</li>
−
</ol>
+
</ul>
−
<hr WIDTH="100%"/>
+
<b>General</b>
−
 
+
<ul>
−
<h3><b>Synchronization Tests</b></h3>
+
<li>Test the various menu actions available for different components</li>
−
 
+
<li>Reload dependancies action from the WSDL Editor menu bar</li>
−
<p>Selection synchronization
+
<li>Test 'Edit Namespaces...' action</li>
−
<ol>
+
<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>
+
<li>Undo/Redo</li>
−
With the design view shown, select from outline - see if design and properties
+
<li>View selection synchronization</li>
−
views are updated</li>
+
<li>Editing synchronization : source -&gt; model (perform source changes below and ensure model is intact)</li>
−
 
+
<ul>
−
<li>
+
<li>cut and paste sections to/from source view</li>
−
With the design view shown, select from design - see if outline and properties
+
<li>make various random changes in the souce view and then undo</li>
−
views are updated</li>
+
<li>delete and restore component declarations from source and ensure references are updated</li>
−
 
+
<li>change a file locally and refresh</li>
−
<li>
+
</ul>
−
Repeat for Source view</li>
+
<li>Editing synchronization : model -&gt; source (perform designical changes below and ensure source is intact)</li>
−
</ol>
+
<ul>
−
</p>
+
<li>make random changes to the WSDL model via the graphical views</li>
−
<p>
+
<li>make various changes in the souce view and then undo</li>
−
Synchronization due to Model Changes
+
</ul>
−
<ol>
+
<li>
−
 
+
F3 support
−
<li>
+
<ul>
−
synchronization tests - change name of element from design - see if outline
+
<li>F3 on component references should cause selection to 'jump' to referenced component</li>
−
and properties are updated</li>
+
<li>F3 on imports should open the imported schema or WSDL</li>
−
 
+
</ul>
−
<li>
+
</li>
−
add/delete from the outline - verify (top level schema view)</li>
+
</ul>
−
 
+
</p>
−
<li>
+
−
edit from tabbed properties - verify views</li>
+
−
 
+
−
<li>
+
−
edit from the source view - ensure the views are updated</li>
+
−
 
+
−
<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 element declarations from source and ensure references
+
−
are updated</li>
+
−
 
+
−
<li>
+
−
change a file locally and refresh</li>
+
−
</ol>
+
−
</p>
+
−
<hr WIDTH="100%"/>
+
−
<h3><b>Design View</b></h3>
+
−
 
+
−
<ol>
+
−
<li>
+
−
drag and drop</li>
+
−
 
+
−
<li>
+
−
drill down elements, complex types, simple types, attributes, attribute
+
−
groups, groups</li>
+
−
 
+
−
<li>
+
−
Top Level View</li>
+
−
 
+
−
<ol>
+
−
<li>
+
−
Actions to add/remove components</li>
+
−
 
+
−
<br/>Menu actions for 'categories' should only provide actions appicable
+
−
to category (e.g. element category should have 'Add Element')
+
−
<li>
+
−
Open Schema action</li>
+
−
 
+
−
<li>
+
−
Direct editing for a newly created 'named' component</li>
+
−
 
+
−
<li>
+
−
Imported components should not appear in 'top level' view</li>
+
−
 
+
−
<li>
+
−
Components with 'structure' should allow 'drill down'</li>
+
−
 
+
−
<li>
+
−
Components with 'null' names should show 'nice' labels</li>
+
−
</ol>
+
−
 
+
−
<li>
+
−
Actions to 'drill down' and return 'Back to Schema View'</li>
+
−
 
+
−
<li>
+
−
In Drilled Down View of Components...</li>
+
−
 
+
−
<ol>
+
−
<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>
+
−
</ol>
+
−
 
+
−
<li>
+
−
Selection from other views should drill down if required</li>
+
−
 
+
−
<ol>
+
−
<li>
+
−
Easy Selection of Simple Types within elements</li>
+
−
</ol>
+
−
 
+
−
</ol>
+
−
 
+
−
<hr WIDTH="100%"/>
+
−
 
+
−
<h3><b>Source View</b></h3>
+
−
 
+
−
<ol>
+
−
<li>
+
−
as-you-type validation</li>
+
−
 
+
−
<li>
+
−
navigation</li>
+
−
 
+
−
<li>
+
−
Test editing features</li>
+
−
 
+
−
<ol>
+
−
<li>
+
−
Add XSD Components</li>
+
−
 
+
−
<li>
+
−
Delete from source</li>
+
−
 
+
−
<li>
+
−
Copy and paste</li>
+
−
 
+
−
<li>
+
−
Test for invalid content</li>
+
−
</ol>
+
−
 
+
−
<li>
+
−
Test 'standard' xml content assist support (see xml source editor) for
+
−
adding schema elements</li>
+
−
 
+
−
<li>
+
−
Test 'schema specific' content assist for the following attribute values...</li>
+
−
 
+
−
<ol>
+
−
<li>
+
−
element 'type' attribute</li>
+
−
 
+
−
<li>
+
−
element 'ref' attribute</li>
+
−
 
+
−
<li>
+
−
model group 'ref' attribute</li>
+
−
 
+
−
<li>
+
−
attribute group 'ref' attribute</li>
+
−
 
+
−
<li>
+
−
complex type's 'base' attribute</li>
+
−
</ol>
+
−
 
+
−
</ol>
+
−
 
+
−
<hr WIDTH="100%"/>
+
−
 
+
−
<h3><b>Properties View</b></h3>
+
−
 
+
−
<ol>
+
−
<li>
+
−
Properties view should be available for all selected schema components</li>
+
−
 
+
−
<li>
+
−
General Tab</li>
+
−
 
+
−
<li>
+
−
Extensions tab</li>
+
−
 
+
−
<li>
+
−
Constraints tab for simple types</li>
+
−
 
+
−
<ul>
+
−
<li>
+
−
Test enumerations</li>
+
−
 
+
−
<li>
+
−
Test patterns</li>
+
−
 
+
−
<li>
+
−
Test facets</li>
+
−
</ul>
+
−
 
+
−
<li>
+
−
Documention tab</li>
+
−
</ol>
+
−
 
+
−
<p/><br/>
+
−
<hr WIDTH="100%"/>
+
−
<h3><b>Outline View</b></h3>
+
−
 
+
−
<ol>
+
−
<li>
+
−
Test that click on a 'drillable top level component' causes drill down</li>
+
−
 
+
−
<li>
+
−
Check content of tree</li>
+
−
</ol>
+
−
<br/>
+
−
<hr WIDTH="100%"/>
+
−
 
+
−
<h3><b>Resource File Tests</b></h3>
+
−
 
+
−
<ol>
+
−
<li>Save</li>
+
−
<li>Save As</li>
+
−
<li>Rename file from navigator view</li>
+
−
<li>Edit file externally</li>
+
−
</ol>
+
−
 
+
−
<br/>
+
−
<hr WIDTH="100%"/>
+
−
 
+
−
<h3><b>Validation</b></h3>
+
−
 
+
−
* as you type validation</li>
+
−
** break references (e.g. type='string' --> type='stringssssssss' to see squiggles
+
−
** fix references to see squiggle go away
+
−
** change component name to break multiple references
+
−
<br/>
+
−
<hr WIDTH="100%"/>
+
−
 
+
−
<h3><b>New XSD Wizard</b></h3>
+
−
 
+
−
<ol>
+
−
<li>
+
−
Create new schemas and ensure file names when prompted are unique for each
+
−
project</li>
+
−
</ol>
+
−
<hr width="100%"/>
+
−
 
+
−
<h3><b>XML Catalog Support</b></h3>
+
−
 
+
−
<ol>
+
−
<li>
+
−
Test that editor respects catalog when resolving schema locations</li>
+
−
 
+
−
<li>
+
−
Test multiple levels of imports</li>
+
−
</ol>
+
−
 
+
−
<hr WIDTH="100%"/>
+
−
 
+
−
<h3><b>General</b></h3>
+
−
 
+
−
<ol>
+
−
<li>
+
−
Set Types Dialog</li>
+
−
 
+
−
<li>
+
−
Set Element Reference Dialog</li>
+
−
 
+
−
<li>
+
−
Undo/Redo</li>
+
−
 
+
−
<li>
+
−
F3 support</li>
+
−
 
+
−
<ol>
+
−
<li>
+
−
From the source view, F3 on component references should cause selection
+
−
to 'jump' to referenced component</li>
+
−
 
+
−
<li>
+
−
F3 on imports or includes should 'open schema'</li>
+
−
 
+
−
<li>
+
−
Double click on an include/import from the design view to open editor</li>
+
−
</ol>
+
−
 
+
−
<li>
+
−
Included components are greyed and menus/properties are read-only</li>
+
−
 
+
−
<li>
+
−
Support for Refactoring</li>
+
−
 
+
−
<ol>
+
−
<li>rename</li>
+
−
 
+
−
<li>make local element global</li>
+
−
 
+
−
<li>make anonymous type global</li>
+
−
 
+
−
</ol>
+
−
</ol>
+
−
 
+
−
<br/>
+
−
<table width="100%"><tr><td valign="top" bgcolor="#0080c0"><big><b><font face="Arial,Helvetica" color="#ffffff">&nbsp;&nbsp;Performance Tests</font></b></big></td>
+
−
</tr></table>
+
−
 
+
−
<h3>Performance Test 1 : Validation</h3>
+
−
# Perform a 'full' validation of a large project (see list of project in Usage Test 2)
+
−
# Open an applicable artifact in the editor and type in the source page to ensure 'as you type' validation is responive
+
−
# Test validation on projects that contain references to external URLs
+
−
# Validate in disconnected mode (no internet access)
+
−
# Run JUnit validation performance tests
+
−
<br/>
+
−
 
+
−
<h3>Performance Test 2 : Opening the Editor</h3>
+
−
# Test how many editors can be opened at once
+
−
#* Import a large project into the workspace with many applicable artifacts
+
−
#* Open an editor for each artifact until you run out of memory (hint : use multi-select and open)
+
−
# Test how how quickly an editor opens
+
−
#* Use a very large artifact
+
−
#* Use an artifact that pulls in lots of other artifacts
+
−
 
+
−
<h3>Performance Test 3 : Editing Responsiveness</h3>
+
−
# Add and Remove elements or types
+
−
#* from the top level view
+
−
#* from the outline
+
−
#* from the source view
+
−
# Typing in the source view
+
−
#* rename an element (type quickly on the keyboard)
+
−
# Open on
+
−
#* from the design view
+
−
#* from the source view
+
−
 
+
−
 
+
−
<h3>Performance Test 4 : Search and Refactoring</h3>
+
−
* Using a mediumm or large sized schema project
+
−
** select a component and test 'refereces->workspace'
+
−
** select a component and refactor->rename (with preview and without)
+
−
** record timings for both 'cold' and 'warm' starts
+

Revision as of 04:06, 5 May 2006


WSDL Component Test Plan
WTP 1.5 Milestone 6

http://www.eclipse.org//webtools/images/wtplogosmall.jpg

  Task Oriented Tests

WSDL M4 Editor test plan

Status of this Document

This is the test plan for the WSDL Editor for the Milestone 4 release. Last updated on 05/04/2006.

Task Oriented Tests

Test Case 1 : Start From Scratch - Standalone

  1. Use the New WSDL Wizard to create a new schema
    (alternative) Use New File to create a blank 'wsdl' file ... everything should still work <p/>
  2. Select a 'target' WSDL that you can attempt to reproduce. Here's some suggestions but feel free to come up with your own <p />

    <p />

  3. Using the target WSDL as a guide, utilize the design view to reproduce it. Attempt to use a top down flow since this best simulates how a user would go about building from scratch (e.g. start with the main elements and types and work your way down to the leaf objects. Be sure to open bugs if... <p />
    • you run into quirky problems that make editing feel unnatural
    • you need to go off to the outline or source view to work around problems
    • you hit performance problems that affect your productivity
    • etc.

    <p />

  4. When you think your WSDL is complete, use the validator to ensure it's valid. Since the editor was used to author the document there should be very few problems. If there are validation problems... <p/>
    • look at the problems carefully and consider why the editor produced these (some of the validation problems are unavoidable but in general the editor should be fairly good at protecting the users against 'bad' schemas)
    • it's likely that the user will need to use the source view to fix them
    • ensure that all problems can be fixed in the source view and that red squggles work (e.g. as you fix things in the source view ensure that red squiggle indicators go away)
    • ensure that when you flip back to the design view that any source changes are reflected in the view

    <p />

  5. As a final test open use the 'jst' tools to generate and deploy a skeletong web services for the WSDL

Test Case 2 : Start From Scratch - One Piece of a Larger Project

  1. Repeat Test Case 1 but recreate a WSDL that's uses a muti-file pattern . Here's some examples... <p>
      Name Where
      SpaceWarGame-b XML Examples Project
      PhoneBanking-b XML Examples Project

    </p> <p />

  2. Be sure to utilize the 'Browse...' function when editing type and element references.
  3. Inspect the schema after using 'Browse...' to ensure that the <include> or <import> and the 'xmlns:xxx' gets updated correctly.
  4. Inspect the source view after using 'Browse...' to ensure the type or element reference is not red squiggled (and muck with it to make sure the squiggle does show when expected)

    5. </ol>

    Test Case 3 : Visualize and Browse a Large/Complex WSDL

    1. Select a WSDL that we want to view.
    2. Use the design view to naviagate the WSDL and open referenced XML Schemas. Ensure all of the following work... <p />
      • click on the 'arrow' beside an element or complex type in the portType ... ensure a schema editor is opened and the 'clicked' object is shown
      • after following a chain of referenes, ensure the 'back arrow' button allows you to reverse back up the chain
      • expand the binding objects to ensure they layout correctly in their 'ruler-ish' form

      <p />

    3. Use the source view to naviage thru the WSDLs and XSDs. Ensure all of the following work... <p>
      • hold down crtl to see the hyperlinks as you mouse over them, ensure hyperlins appear for all 'references'
      • ctrl-lick or F3 on hypelinksto ensure 'open on' works
      • after following a chain of referenes, ensure the 'back arrow' button allows you to reverse back up the chain

      </p>

    4. Navigate thru the WSDLs and XSDs using both the design and source view (flipping between 'em) and ensure both modes of navigation work together nicely.
    5. Use the outline view in conjuction and ensure it interacts as expected with the source and design view
    6. From the source, design and outline views. Use the 'references->project' or 'references->workspace' for several components (portTypes, bindings, types, elements etc.) to understand how components are reused.

      7. </ol>

      Function Oriented Tests

      New WSDL Wizard

      • Try the various options available on the New WSDL file options page
        • option to create WSDL Skeleton
        • SOAP...document literal, rpc literal, rpc encoded
        • HTTP...HTTP GET, HTTP POST

      design View

      • Top Level View
        • Actions to add/remove/rename components
        • Open Schema/WSDL Imports
        • Imported WSDL components should appear but not be editable
        • Inline Schemas located in the 'top level' view should allow drill down
        • Connecting lines should appear to show WSDL component relationships
      • In Drilled Down View of Schema Components...
        • Test that menus show proper content for different objects
        • Test Drag and Drop
        • Ensure deleting the 'top level' component pops you back to the top view
        • Test selection of 'simple type' icon within an element declaration
        • Content that originates via derivation should be demarked with dotted box

      Outline View

      • Selection from Outline view should select the corresponding object in the design view
      • Context menu for a particular component should be the same in both the design and Outline views

      Source View

      • Test editing features
        • Add WSDL Components
        • Delete from source
        • Copy and paste
        • Test for invalid content
      • Test 'standard' xml content assist support (see xml source editor) for adding WSDL and schema elements

      Properties View

      • Properties view should be available for all selected schema components
      • Test that view can't be 'broken'... should always have 'good' content
      • Imported WSDL components should not be editable through the properties
      • Renaming components should 'auto refactor' within source file (references to renamed component should be updated)
      • Update documentation for various components

      Set Existing Component Dialog

      • Set Existing Component Dialog launched via the context menu or properties
        • Port
        • Binding
        • Input
        • Output
        • Fault
        • Part
      • Adjust the search scope. The available components displayed should be updated
      • The text filter located at the top of the dialog is used to filter the available types

      Generate Binding Content

      • 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
      • Test out the different Binding options (SOAP, HTTP, etc...)

      Smart Renaming

      • Test smart renaming on the following Components
        • Operation
        • Fault
        • Message
        • Part
      • 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)
      • The same pattern follows when renaming a Fault, Message, and Part
      • Initiate renaming via the context menu or the properties view

      General

      • Test the various menu actions available for different components
      • Reload dependancies action from the WSDL Editor menu bar
      • Test 'Edit Namespaces...' action
      • Add 'import and test that 'new' components are available in the 'set type' dialog
      • Menu actions for 'categories' should only provide actions appicable to that particular category (e.g. element category should have 'Add Element')
      • Undo/Redo
      • View selection synchronization
      • Editing synchronization : source -> model (perform source changes below and ensure model is intact)
        • cut and paste sections to/from source view
        • make various random changes in the souce view and then undo
        • delete and restore component declarations from source and ensure references are updated
        • change a file locally and refresh
      • Editing synchronization : model -> source (perform designical changes below and ensure source is intact)
        • make random changes to the WSDL model via the graphical views
        • make various changes in the souce view and then undo
      • F3 support
        • F3 on component references should cause selection to 'jump' to referenced component
        • F3 on imports should open the imported schema or WSDL

Retrieved from "https://wiki.eclipse.org/index.php?title=WSDL_Test_Plan&oldid=4645"

Back to the top