Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

XSD Test Plan

Revision as of 12:37, 8 October 2008 by Unnamed Poltroon (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

XSD Component Test Plan
WTP 1.5 Final

  Task Oriented Tests

Test Case 1 : Start From Scratch

  1. 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

  2. Select a 'target' schema that you can attempt to reproduce. Here's some suggestions but feel free to come up with your own
      Description Where
      GolfCourse XML Examples Project
      SpaceWarGame XML Examples Project
      OrgChart XML Examples Project

  3. 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...
    • 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.

  4. When you think your schema is complete, use the validator to ensure it's valid.
    • 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.
    • some of the validation problems are unavoidable but in general the editor should be fairly good at protecting the users against 'bad' schemas)
    • if there are problems 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
    • 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 view changes are reflected in the design view

  5. As a final test open an XML file that validates for the 'target' 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.

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

  1. Repeat Test Case 1 but recreate a schema that's a part of a multi-schema project. Here's some examples...
      Name Where
      SpaceWarGame-b XML Examples Project
      oagis-8 link
  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)

Test Case 3 : Visualize and Browse a Large Schema

  1. Select a schema that we want to view.

  2. Use the design view to naviagate thru the schema(s). Ensure all of the following work...
    • click on items listed in the top level view to ensure 'open on' works
    • double click on type headers to 'open on' works
    • after following a chain of referenes, ensure the 'back arrow' button allows you to reverse back up the chain
    • as you navigate ensure the design view displays the correct thing and the layout and line routing is correct

  3. Use the source view to naviage thru the schema(s). Ensure all of the following work...
    • 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

  4. Browse the schema(s) by flipping between both the design and source view and ensure source view and design view navigation work together nicely.

  5. Use the outline view in conjuction with the source and design view.

  6. From the source, design and outline views. Use the 'references->project' or 'references->workspace' for several components (types, elements etc.) to understand how components are reused in the schema(s).

Test Case 4 : Refactor a large schema project

  1. a) Select one of the existing refactoring 'before and after' projects form the list below
    -- or ---
    b) Use any project and come up with a reorganization 'plan' (change names, move things around etc.) that will describe your 'target' project.
  2. Use the editor's editing and refactoring support to make the existing project look like the 'target' project.
  3. After each refactoring is applied ensure that the project validates.

  Function Oriented Tests

Actions Tests

  1. from top level view test Adding each kind of component
  2. from an element test the Set Type action
  3. from a complex type test Adding an element, attribute, sequence and choice
  4. from various contexts test the Delete action
  5. show properties
  6. set type / set element / set element ref
  7. set multiplicity
  8. from the schema test the Edit Namespaces... action (from properties)

Synchronization Tests

Selection synchronization

  1. With the design view shown, select from outline - see if design and properties views are updated
  2. With the design view shown, select from design - see if outline and properties views are updated
  3. Repeat for Source view

Synchronization due to Model Changes

  1. synchronization tests - change name of element from design - see if outline and properties are updated
  2. add/delete from the outline - verify (top level schema view)
  3. edit from tabbed properties - verify views
  4. edit from the source view - ensure the views are updated
  5. cut and paste sections to/from source view
  6. make various random changes in the souce view and then undo
  7. delete and restore element declarations from source and ensure references are updated
  8. change a file locally and refresh

Design View

  1. drag and drop
  2. drill down elements, complex types, simple types, attributes, attribute groups, groups
  3. Top Level View
    1. Actions to add/remove components

    2. Menu actions for 'categories' should only provide actions appicable to category (e.g. element category should have 'Add Element')

    3. Open Schema action
    4. Direct editing for a newly created 'named' component
    5. Imported components should not appear in 'top level' view
    6. Components with 'structure' should allow 'drill down'
    7. Components with 'null' names should show 'nice' labels
  4. Actions to 'drill down' and return 'Back to Schema View'
  5. In Drilled Down View of Components...
    1. Test that menus show proper content for different objects
    2. Test Drag and Drop
    3. Ensure deleting the 'top level' component pops you back to the top view
    4. Test selection of 'simple type' icon within an element declaration
    5. Content that originates via derivation should be demarked with dotted box
  6. Selection from other views should drill down if required
    1. Easy Selection of Simple Types within elements

Source View

  1. as-you-type validation
  2. navigation
  3. Test editing features
    1. Add XSD Components
    2. Delete from source
    3. Copy and paste
    4. Test for invalid content
  4. Test 'standard' xml content assist support (see xml source editor) for adding schema elements
  5. Test 'schema specific' content assist for the following attribute values...
    1. element 'type' attribute
    2. element 'ref' attribute
    3. model group 'ref' attribute
    4. attribute group 'ref' attribute
    5. complex type's 'base' attribute

Properties View

  1. Properties view should be available for all selected schema components
  2. General Tab
  3. Extensions tab
  4. Constraints tab for simple types
    • Test enumerations
    • Test patterns
    • Test facets
  5. Documention tab


Outline View

  1. Test that click on a 'drillable top level component' causes drill down
  2. Check content of tree

Resource File Tests

  1. Save
  2. Save As
  3. Rename file from navigator view
  4. Edit file externally


  • 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

New XSD Wizard

  1. Create new schemas and ensure file names when prompted are unique for each project

XML Catalog Support

  1. Test that editor respects catalog when resolving schema locations
  2. Test multiple levels of imports


  • General
    1. Test adding imports via the outline/design/properties and source view (and verify they show up in all other views)
    2. Verify new components are available in the 'set type' dialog
    3. Test adding them via the 'set type' dialog will add import to the xsd
    4. Unused imports - new to 3.0
      • Check preferences under Web Services->XML Schema Files
      • Test that unused XSD imports are removed
      • Test that redefines are not removed.
  • Schema with null targetNamespaces
    1. Set type on element from schema with null namespace
    2. Set element reference from schema with null namespace


  1. Set Types Dialog
  2. Set Element Reference Dialog
  3. Undo/Redo
  4. F3 support
    1. From the source view, F3 on component references should cause selection to 'jump' to referenced component
    2. F3 on imports or includes should 'open schema'
    3. Double click on an include/import from the design view to open editor
  5. Included components are greyed and menus/properties are read-only
  6. Support for Refactoring
    1. rename
    2. make local element global
    3. make anonymous type global

  Performance Tests

Performance Test 1 : Validation

  1. Perform a 'full' validation of a large project (see list of project in Usage Test 2)
  2. Open an applicable artifact in the editor and type in the source page to ensure 'as you type' validation is responive
  3. Test validation on projects that contain references to external URLs
  4. Validate in disconnected mode (no internet access)
  5. Run JUnit validation performance tests

Performance Test 2 : Opening the Editor

  1. 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)
  2. Test how how quickly an editor opens
    • Use a very large artifact
    • Use an artifact that pulls in lots of other artifacts

Performance Test 3 : Editing Responsiveness

  1. Add and Remove elements or types
    • from the top level view
    • from the outline
    • from the source view
  2. Typing in the source view
    • rename an element (type quickly on the keyboard)
  3. Open on
    • from the design view
    • from the source view

Performance Test 4 : Search and Refactoring

  • 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

Back to the top