| <?xml version="1.0" encoding="utf-8"?> |
| <?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?> |
| <html> |
| <head> |
| <meta name="root" content="../../../www/" /> |
| <title>XSD WTP 2.0 final test plan</title> |
| </head> |
| <body> |
| <h1>XSD WTP 2.0 final test plan</h1> |
| <h2>Status of this Plan</h2> |
| <p>Proposed Plan (5.14.07)</p> |
| |
| <h2>Overall goals</h2> |
| <h3> |
| <b>Co-developer Testing</b> |
| </h3> |
| <p> |
| We will inspect "runtime" version of build to be |
| sure extra source is not included, and more important, we'll |
| inspect and test importing SDK version to be sure all |
| relevant "open source" is included in that SDK |
| build and that it correctly imports into a development |
| environment. |
| </p> |
| <h3> |
| <b>End User Testing</b> |
| </h3> |
| <p> |
| The nature of the end-user testing is intentionally planned |
| to be "ad hoc" instead of specifying step by step "how to" |
| directions and specific "expected results" sections often |
| seen in test cases. This is done because its felt leads to |
| greater number of "paths" being tested, and allows end-users |
| more motivation for logging "bugs" if things didn't work as |
| <i>they</i> |
| expected, even if it is working as designed. |
| </p> |
| |
| <p> |
| As we progress through milestones, we'll add more and more |
| detail for special cases, special files, special projects, |
| etc.When we do have special or sample test files and |
| projects, we will keep those stored in CVS, as projects |
| under a |
| <i>testdata</i> |
| directory under the |
| <i>development</i> |
| directory of relevant component so that testers (from |
| immediate team, or community) can easily check out into the |
| environment being tested. |
| </p> |
| |
| <h3> |
| <b>Platform Testing</b> |
| </h3> |
| <p> |
| While we do not have any platform specific code, or |
| function, we will have some team members do end-user tests |
| on Linux, some on Windows. We will also confirm unit tests |
| pass on both platforms. |
| </p> |
| |
| <h3> |
| <b>Performance Testing</b> |
| </h3> |
| <p> |
| We have added (some) automated performance tests along the |
| lines of the Eclipse base performance unit tests in future |
| milestones. These are currently in the |
| <b>org.eclipse.wst.xsd.tests.performance</b> |
| plugin. |
| <br /> |
| <br /> |
| We will continue to add more test cases in upcoming |
| milestones. |
| </p> |
| <h2>Testing focus for 2.0</h2> |
| <ul> |
| <li>Design |
| <ul> |
| <li> |
| Test inheritance of complex and simple types |
| </li> |
| <li> |
| Test set new type dialog on an attribute |
| </li> |
| <li> |
| Test set new type dialog on an element in a no namespace schema |
| </li> |
| <li> |
| Test layout of schema index view |
| </li> |
| <li> |
| Test drag and drop of elements and attributes |
| </li> |
| <li> |
| Test the "Export Diagram as Image" capability by clicking on the icon in the toolbar |
| </li> |
| <li> |
| Test selection/direct edit of newly added element of a complex type, and ensure it is the correct one |
| if the complex type figure is shown multiple times in the view |
| </li> |
| </ul> |
| </li> |
| <li>Source |
| <ul> |
| <li> |
| Test F3/hyperlink support |
| </li> |
| </ul> |
| </li> |
| <li>Properties |
| <ul> |
| <li> |
| Test extensions view combo boxes and ensure the choices are correct |
| </li> |
| <li> |
| Test mixed attribute value in Advanced Properties of a complex type |
| </li> |
| </ul> |
| </li> |
| <li>Validation - verify XSD validation works properly</li> |
| </ul> |
| <h2>XSD Tests</h2> |
| <ul> |
| <li> |
| WTP 2.0 XSD Smoke Tests <a href="http://wiki.eclipse.org/XSD_Smoke_Test_Scenarios">here</a> |
| </li> |
| <li> |
| Test the editing capabilities of the Design, Source, Outline, and Properties view. |
| Ensure all views are also updated appropriately after the editing action |
| </li> |
| <li> |
| Test Design page, Source page, Outline view, Properties |
| view synchronization |
| </li> |
| <li> |
| Content assist - In the source view, place the cursor |
| in various places in the source. Ensure content assist (Ctrl + Space) |
| populates the list of available content to add is appropriate |
| for the cursor location. |
| <ul> |
| <li>element type</li> |
| <li>attribute type</li> |
| <li>element ref</li> |
| <li>type base</li> |
| </ul> |
| </li> |
| <li> |
| Test XSD validation. Right click on a XSD file and choose the option to |
| validate. Validate both correct and incorrect XSD files. |
| </li> |
| <li> |
| Test New XSD Wizard. Ensure unique filenames are proposed. |
| </li> |
| <li> |
| Refactoring |
| <ul> |
| <li>Test rename refactor on references made to XSD components</li> |
| <li>Test making anonymous types global</li> |
| <li>Test making local element global</li> |
| </ul> |
| </li> |
| <li> |
| Profiling: |
| <ul> |
| <li> |
| Test basic editor functions and look for problem |
| areas (large memory consumption, intense cpu usage) |
| </li> |
| </ul> |
| </li> |
| <li> |
| Ensure editing cannot be done on read-only components |
| </li> |
| <li> |
| Test Undo/Redo |
| </li> |
| <li> |
| XML Catalog |
| <ul> |
| <li>Test schemas in a jar in the catalog</li> |
| <li>Test schemas in the catalog</li> |
| </ul> |
| </li> |
| <li> |
| End to end scenario - Create a schema from scratch and try recreating an industry standard schema |
| </li> |
| <li> |
| Preferences - Test XSD preferences page |
| </li> |
| <li> |
| Navigation - test navigation history of the graph view. |
| </li> |
| <li> |
| Properties - test the properties views of all schema components |
| </li> |
| <li> |
| </li> |
| </ul> |
| </body> |
| </html> |
