Skip to main content

WSDL Editor wtp 2.0 final test plan

WSDL Editor wtp 2.0 final test plan
WTP LogoWTP Home

Status of this Plan

Proposed Plan (5.14.07)

Overall goals

End User Testing

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 they expected, even if it is working as designed.

Platform Testing

While we do not have any platform specific code, or function, we will have some team members do end-user tests on Linux and on Windows.

Testing focus for 2.0

  • Verify rename refactor operations on WSDL components which can be referenced works
  • Verify content assist works
  • Verify New WSDL Wizard works properly
  • Verify all views are synchronized
  • Verify binding generation works properly
  • Verify WSDL validation works properly

WSDL Editor Tests

  • Test Design view, Source view, Outline view, Properties view synchronization. Selecting various components in each of the views and ensuring the other views also display the newly selected object
  • Check 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. Make sure to check with the cursor location in an inline schema location
  • Check WSDL validation. Right click on a WSDL file and choose the option to validate. Validate both correct and incorrect WSDL files
  • Test hyperlink. In the Source view, place the cursor on referenced components and press F3. Also test out the Ctrl + left mouse click method of activating the hyperlink
  • New WSDL Wizard:
    • Make sure the Wizard creates a valid WSDL file when the generate skeleton option is selected. Test this with the various generation options. For example, SOAP, HTTP, Doc-literal, HTTP Post, etc...
    • Test the Wizard with the generate skeleton option unselected
  • Rename refactor
    • Test rename refactor on references made to WSDL components
    • Test rename refactor on references made to Schema components
  • Profiling:
    • Test basic editor functions and look for problem areas (large memory consumption, intense cpu usage)
  • Test the editing capabilities of the Deisgn, Source, Outline, and Properties view. Ensure all views are also updated appropriately after the editing action
  • Test the "Export Diagram as Image" capability by clicking on the icon in the toolbar
  • Test the Schema object preview by hovering over the Schema link icon (arrow) located to the right of the Porttype box
  • Test the schema integration. Cock on the Schema link icon (arrow) located to the right of the Porttype box. An external XSD Editor should appear
  • Ensure editing cannot be done on read-only components

XML Examples

  • Create the Editing and validating XML files Examples
  • Verify that the sample files are created in the designated folder

Back to the top