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 pages "WSDL Test Plan" and "Main Page"

(Difference between pages)
 
 
Line 1: Line 1:
<table width="100%">
+
Welcome to the Eclipsepedia - the Eclipse.org Wiki. You can browse the Wiki anonymously, but you must log in using your Eclipse Bugzilla account to edit pages.  If you don't have a Bugzilla account, you can [https://bugs.eclipse.org/bugs/createaccount.cgi create one here].
<tr>
+
<td width="80%" align="top">
+
<br><b><big>WSDL Editor test plan</big></b>
+
<br><b><big>WTP 1.5 Milestone 6</big></b>
+
<td>
+
http://www.eclipse.org//webtools/images/wtplogosmall.jpg
+
</td>
+
</tr>
+
</table>
+
<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>
+
<h3>Test Case 1 : Start From Scratch</h3>
+
<ol>
+
<li>
+
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
+
<br/>
+
</li>
+
<br/>
+
<li>Select a 'target' schema that you can attempt to reproduce. Here's some suggestions but feel free to come up with your own
+
  
<ul>
 
  <table border='1'>
 
    <tr bgcolor="#CCCCCC">
 
      <td>Description</td>
 
      <td>Where</td>
 
    </tr>
 
    <tr> 
 
      <td>GolfCourse</td>
 
      <td>XML Examples Project</td>
 
    </tr>
 
    <tr> 
 
      <td>SpaceWarGame</td>
 
         
 
      <td>XML Examples Project</td>
 
    </tr>
 
    <tr> 
 
      <td>OrgChart</td>
 
      <td>XML Examples Project</td>
 
    </tr>   
 
  </table> 
 
</ul>
 
</li>
 
<br/>
 
<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
 
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).
 
Be sure to open bugs if...
 
  
<ul>
+
= Official Eclipse FAQs =
  <li>you run into quirky problems that make editing feel unnatural</li>
+
* [[The Official Eclipse FAQs | Official Eclipse FAQs]] 
  <li>you need to go off to the outline or source view to work around problems</li>
+
  <li>you hit performance problems that affect your productivity</li>
+
  <li>etc.</li>
+
</ul>
+
  
</li>
+
= Project Wiki pages =
<br/>
+
<li>When you think your schema is complete, use the validator to ensure it's valid.
+
<ul>
+
  <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>some of the validation problems are unavoidable but in general
+
the editor should be fairly good at protecting the users against 'bad'
+
schemas)</li>
+
<li>if there are problems it's likely that the user will need to use
+
the source view to fix them</li>
+
<li>ensure that all problems can be fixed in the source view and that
+
red squggles work</li>
+
<li>as you fix things in the source view ensure that red squiggle indicators
+
go away</li>
+
<li>ensure that when you flip back to the design view that any source
+
view changes are reflected in the design view</li>
+
</ul>
+
  
</li>
+
== A ==
<br/>
+
* [[ALF| Application Lifecycle Framework Project]]
<li>As a final test open an XML file that validates for the 'target'
+
* [[AspectJ/AJDT| AspectJ and AJDT Projects]]
schema and edit a copy so that it point to the 'new' schema. Ensure
+
the XML file validates against the 'new' schema.  If it doesn't validate
+
ensure the schema editor helps you fix the problems.
+
</li></ol>
+
----
+
  
<h3><b>Test Case 2 : Start From Scratch - One Piece of a Larger Project</b></h3>
+
== B ==
<ol>
+
* [[BIRT Project| BIRT Project]]
<li>Repeat Test Case 1 but recreate a schema that's a part of a multi-schema project. Here's some examples...
+
* [http://wiki.tada.se/display/buckminster/Home Buckminster Project]
<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>oagis-8</td>
+
      <td>[http://www.openapplications.org/downloads/oagidownloads.htm link]</td>
+
    </tr>
+
  </table>
+
</ul>
+
</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>
+
<br/>
+
----
+
  
<h3><b>Test Case 3 : Visualize and Browse a Large Schema</b></h3>
+
== C ==
<ol>
+
* [[CDT|CDT Project]]
<li>Select a schema that we want to view.
+
* [[Corona|Corona Project - Tool Services Framework]]
</li>
+
<br/>
+
<li>Use the design view to naviagate thru the schema(s). Ensure all of the following work...
+
<br/>
+
<ul>
+
  <li>click on items listed in the top level view to ensure 'open on' works</li>
+
  <li> double click on type headers to 'open on' works</li>
+
  <li> after following a chain of referenes, ensure the 'back arrow' button
+
allows you to reverse back up the chain</li>
+
  <li>as you navigate ensure the design view displays the correct thing
+
      and the layout and line routing is correct</li>     
+
</ul>
+
<br/>
+
<li>Use the source view to naviage thru the schema(s). Ensure all of the following work...
+
<br/>
+
<ul>
+
  <li>hold down crtl to see the hyperlinks as you mouse over them, ensure
+
hyperlins appear for all 'references'
+
  </li>
+
  <li>ctrl-lick or F3 on hypelinksto ensure 'open on' works</li>
+
  <li>after following a chain of referenes, ensure the 'back arrow' button
+
allows you to reverse back up the chain</li>
+
</ul>
+
</li>
+
<br/>
+
<li>Browse the schema(s) by flipping between both the design and source
+
view and ensure source view and design view navigation work together nicely.
+
</li>
+
<br/>
+
<li>Use the outline view in conjuction with the source and design view.
+
</li>
+
<br/>
+
<li>From the source, design and outline views. Use the 'references-&gt;project'
+
or 'references->workspace' for several components (types, elements etc.)
+
to understand how components are reused in the schema(s).
+
</li>
+
</li>
+
</ol>
+
----
+
<h3><b>Test Case 4 : Refactor a large schema project</b></h3>
+
<ol>
+
<li>a) Select one of the existing refactoring 'before and after' projects form the list below
+
<br/>-- or ---
+
<br/>b) Use any project and come up with a reorganization 'plan' (change
+
names, move things around etc.) that will describe your 'target' project.
+
</li>
+
<li>Use the editor's editing and refactoring support to make the existing
+
project look like the 'target' project.
+
</li>
+
<li>After each refactoring is applied ensure that the project validates.
+
</li>
+
</ol>
+
__NOTOC__
+
  
<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>
+
== D ==
</tr></table>
+
* [[Dali Project | Dali EJB ORM Project]]
 +
* [[Dash | Dash Proposal]]
 +
* [[Data Tools Platform Project]]
 +
* [[DSDP|DSDP Top-Level Project]]
  
<h3><b>Actions Tests</b></h3>
+
== E ==
 +
* [[Eclipse Communication Framework Project]]
 +
* [[Eclipse Modeling Framework | Eclipse Modeling Framework Project]]
 +
* [[Eclipse Modeling Framework Technologies | Eclipse Modeling Framework Technologies Project]]
 +
* [[Eclipse Project| Eclipse Project]]
 +
* [[Equinox| Equinox Project]]
  
<ol>
+
== G ==
<li> from top level view test <b>Add</b>ing each kind of component </li>
+
* [[Graphical Editing Framework | Graphical Editing Framework Project]]
<li> from an element test the <b>Set Type</b> action </li>
+
* [[Graphical Modeling Framework | Graphical Modeling Framework Project]]
<li> from a complex type test <b>Add</b>ing an element, attribute, sequence and choice</li>
+
<li> from various contexts test the <b>Delete</b> action </li>
+
<li> show properties</li>
+
<li> set type / set element / set element ref</li>
+
<li> set multiplicity</li>
+
<li> from the schema test the <b>Edit Namespaces...</b> action (from properties)</li>
+
</ol>
+
<hr WIDTH="100%"/>
+
  
<h3><b>Synchronization Tests</b></h3>
+
== H ==
 +
* [[Higgins Trust Framework Project|Higgins Project]]
  
<p>Selection synchronization
+
== M ==
<ol>
+
* [[Mylar|Mylar Project]]
  
<li>
+
== O ==
With the design view shown, select from outline - see if design and properties
+
* [[OHF|Open Healthcare Framework]]
views are updated</li>
+
  
<li>
+
== P ==
With the design view shown, select from design - see if outline and properties
+
* [[Parallel_Tools_Platform | Parallel Tools Platform Project]]
views are updated</li>
+
* [[Phoenix | Phoenix Project]]
  
<li>
+
== R ==
Repeat for Source view</li>
+
* [[Release Engineering | Release Engineering]]
</ol>
+
</p>
+
<p>
+
Synchronization due to Model Changes
+
<ol>
+
  
<li>
+
== S ==
synchronization tests - change name of element from design - see if outline
+
* [[STP| SOA Tools Platform Project]]
and properties are updated</li>
+
  
<li>
+
== T ==
add/delete from the outline - verify (top level schema view)</li>
+
* [[DSDP/TM| Target Management Project]]
  
<li>
+
== U ==
edit from tabbed properties - verify views</li>
+
* [[UML2 | UML2 Project]]
  
<li>
+
== V ==
edit from the source view - ensure the views are updated</li>
+
* [[Visual Editor Project]]
  
<li>
+
== W ==
cut and paste sections to/from source view</li>
+
* [[Web Tools Project|Web Tools Platform Project]]
  
<li>
+
= Other Wiki pages =
make various random changes in the souce view and then undo</li>
+
* [[Kudos]]
 +
* [[Development Resources]]
 +
* [[Getting Involved with the Community]]
 +
* [[IRC]]
 +
* [[Foundation|Eclipse Foundation]]
 +
* [[Eclipse Conferences]]
 +
* [[Rich Client Platform]] (RCP)
 +
* [http://eclipsewiki.editme.com/GoogleSummerOfCode2006 Google Summer of Code 2006]
  
<li>
+
= Elsewhere at eclipse.org =
delete and restore element declarations from source and ensure references
+
[http://www.eclipse.org/ Eclipse.org home]
are updated</li>
+
  
<li>
+
[http://planeteclipse.org/planet/ PlanetEclipse] - [[PlanetEclipseAdmins]]
change a file locally and refresh</li>
+
</ol>
+
</p>
+
<hr WIDTH="100%"/>
+
<h3><b>Design View</b></h3>
+
  
<ol>
+
The content on this Wiki is governed by the Eclipse.org [http://www.eclipse.org/legal/termsofuse.php Terms of Use]
<li>
+
drag and drop</li>
+
  
<li>
+
Please see the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for usage and configuration help.
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>
+
 
+
<li>
+
</li>
+
</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>
+
 
+
<li>
+
</li>
+
</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>
+
Edit file externally</li>
+
</ol>
+
 
+
<br/>
+
<hr WIDTH="100%"/>
+
 
+
<h3><b>Validation</b></h3>
+
 
+
<ol>
+
<li>
+
as you type validation</li>
+
 
+
<li>
+
change type from string to stringssssssss to see squiggles</li>
+
 
+
<li>
+
</li>
+
</ol>
+
 
+
<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 : Large Models </h3>
+
# Open the editor on a large artifact
+
# Open the editor on an artifact that 'pulls in' lots of other artifacts
+

Revision as of 14:10, 5 May 2006

Welcome to the Eclipsepedia - the Eclipse.org Wiki. You can browse the Wiki anonymously, but you must log in using your Eclipse Bugzilla account to edit pages. If you don't have a Bugzilla account, you can create one here.


Official Eclipse FAQs

Project Wiki pages

A

B

C

D

E

G

H

M

O

P

R

S

T

U

V

W

Other Wiki pages

Elsewhere at eclipse.org

Eclipse.org home

PlanetEclipse - PlanetEclipseAdmins

The content on this Wiki is governed by the Eclipse.org Terms of Use

Please see the User's Guide for usage and configuration help.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.