# '''As you type validation''': add invalid attributes or elements to the XML Schema. As you type them, the text should be underlined in red and on mouseover, an error message should be displayed (if you already verified as you type validation while you were verifying validation, you can skip this step)

# '''As you type validation''': add invalid attributes or elements to the XML Schema. As you type them, the text should be underlined in red and on mouseover, an error message should be displayed (if you already verified as you type validation while you were verifying validation, you can skip this step)

# '''Content Assist''': use CTRL+SPACE in various parts of the Schema to see the possible entries that can be added

# '''Content Assist''': use CTRL+SPACE in various parts of the Schema to see the possible entries that can be added

−

# '''Context menus''': right click in the Design, Outline, and Source view to check the context menus

−

# '''Formatting''': in the Source view, right click -> source -> Format. Now untab some elements by selecting elements and using SHIFT+TAB. To reformat, right click -> source -> Format.

# '''Switching between Design and Source view''': make sure changes to the source are reflected in the Design view

# '''Switching between Design and Source view''': make sure changes to the source are reflected in the Design view

Revision as of 16:33, 12 June 2009

The smoke tests are organized into three categories: core tests, secondary rotating tests and adhoc tests. In every test run, the goal is to devote 60% of the time to core tests from which every test should be run, 30% to secondary rotating tests from which a tester can pick two or three tests making sure to cover each test at least once in a milestone, and 10% to adhoc test which can be picked randomly.

Right click in the Element section and add a new element called NewElement and add a NewComplexType in the Types section as well

Save and close the editor

Reopen the editor and verify that the NewElement and NewComplexType are persisted.

File -> Save As..., and use the name NewXMLSchemaSaveAs.xsd

Verify the NewXMLSchemaSaveAs.xsd file appear in the navigator

In NewXMLSchemaSaveAs.xsd, add a new element and a new complex type

Close the editor without saving the changes

Reopen the NewXMLSchemaSaveAs.xsd, and verify that the new changes are discarded

Selection Tests

Synchronization between Properties, Design, Source, and Outline views: while conducting the Add/Modify tests, delete tests, and drag & drop tests, observe that these three views are synchronized

Note: if the nodes are collapsed and you add a new child, the node will not automatically expand. Therefore to test synchronization, expand the nodes whenever necessary to verify the synchronization between the Outline and Design view

Add/Modify Tests

For the tests where a new item is added:

Verify that the item was successfully added by finding and selecting the item from the Outline view or Design view

Whenever possible, modify the name of the item by changing the Name property in the Properties view under General properties

Tests:

Include: create a copy of the XML schema of interest and copy to another workspace directory. In Outline view, right click on the Directives node -> Add Include. In the Properties view, select the copied schema as the Schema location

Import: in Outline view, right click on the Directives node -> Add Import. Select a schema from the workbench

Redefine: in Outline view, right click on the Directives node -> Add Redefine. Select a schema from the workbench

Element: in Outline view, right click on the Elements node -> Add Element

Attribute: in Outline view, right click on the Attributes node -> Add Attribute

Attribute Group: in Outline view, right click on the Attributes node -> Add Attribute Group. Right click on the newly created Attribute Group -> Add Attribute

Attribute default and fixed values: right click on an Attribute -> select the Default radio button from the Properties view under the General vertical tab -> Put a value. Verify changes by going to Source view. Now change the radio button to Fixed and verify the change in the source view.

Attribute ref default and fixed values: right click on an Attribute ref -> select the Default radio button from the Properties view under the General vertical tab -> Put a value. Verify changes by going to Source view. Now change the radio button to Fixed and verify the change in the source view.

Attribute group ref: in Outline view, right click on a Complex Type -> Add Attribute Group Ref

Any Attribute: in Outline view, right click on a Complex Type -> Add Any Attribute

Sequence: in Outline view, right click on a Complex Type -> Add Sequence

Choice: in Outline view, right click on a Complex Type -> Add Choice

All: in Outline view, right click on a Complex Type -> Add All

Repeat the same steps for Design View. The UI element to mouseover and right click for each test is highlighted when selected in the Outline view

Delete locals and globals: Delete locals by removing a non-root element from the XML schema document and remove globals by removing a root element from the XML schema. Remove by right clicking on the element -> Delete

Secondary Rotating Tests

Two or three tests from this category should be run in every smoke test. Testers should make sure every test should be run at least once in any given milestone.

Drag & Drop Tests

Sequence: setup by creating a new Complex Type, adding a sequence, and adding a few elements into the sequence. In the Design view, re-order the sequence elements by dragging.

Group: setup by creating a new Group and adding a few elements. In the Design view, re-order the sequence elements by dragging.

Attribute: setup by creating a new Complex Type and adding a few attributes. In the Design view, re-order the attributes by dragging.

Attribute group: setup by creating a new Attribute Group and adding a few attributes. In the Design view, re-order the attributes by dragging.

The reordering must be reflected in the bothe the Design and Outline view and in the editor's Source view.

Source Editing

As you type validation: add invalid attributes or elements to the XML Schema. As you type them, the text should be underlined in red and on mouseover, an error message should be displayed (if you already verified as you type validation while you were verifying validation, you can skip this step)

Content Assist: use CTRL+SPACE in various parts of the Schema to see the possible entries that can be added

Switching between Design and Source view: make sure changes to the source are reflected in the Design view

Hyperlink Navigation

Referenced components: in the Source View, press F3 or "CTRL+click" over a referenced component. The source editor should go to the referenced component

Imports and Includes in the Source View: in the Source View, press F3 or "CTRL+click" over an import or include and the selection should jump to the referenced component

Imports and Includes in the Design View: in the Design View, double click on an include or import, which will automatically open the editor

Extensions

Add extensions: right click on a Complex Type -> select the Extension vertical tab from the Properties view -> under Extension, click the Add button -> click Add in the ADd Extension Components menu -> fill in a name -> select a schema from the workspace -> Click OK until you return to the Add Extension Components menu -> select a component from the Available components to Add list and press OK

Add extension attribute: Note: uses results from previous step. From the instructions above, add an attribute by selecting an Extension from the list -> Fill in a value for any values that show up in the Extension Details list, which is to the right of the Extensions list

Delete extensions: Note: uses results from previous step. Right click on an Extension in the Extensions list -> Remove

XML Catalog

Load an XML schema from the jar: create a new XML Schema or use an existing XML schema -> select Extensions from the vertical tab in the Properties view -> Add -> Add... -> fill in a schema name -> select a Schema from Catalog (these schema documents are from jar files). Not all schemas will have components, so select schemas like http://schemas.xmlsoap.org/wsdl/ -> a component should show up in the Available components to Add list, select one and press OK. Check that the imported schema shows up in the Source view and the component added

Export XML catalog file: right click on a project in the Package Explorer view -> Export... -> select the XML Catalog from the XML folder and press the Next button -> select a directory to export file to and add a name which ends in .xml -> press the Finish button. Open the newly export XML Catalog File and verify that it isn't empty (should contain the element <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/>)

Import XML catalog file: right click on a project in the Package Explorer view -> Import... select the XML Catalog from the XML folder and press the Next button -> select a directory -> press the Import Files... button -> Use browse to find the location of an XML Catalog file -> select the XML file(s) -> click the Finish button. Verify the files were added into the correct directory and contain the correct information. A quick way to export files is to use files in the same workspace but export to a different directory within the project

Generators

Generate an XML file from an XSD file: right click on an XML Schema -> Generate -> XML File... -> Add a new file name or use default and press the Next button -> press the Finish button. From the example files, GolfCountryClub.xsd will generate a decent number of elements

Validate this file and notice that an error is displayed (prefixed by cos-nonambig). By default the preference "Check full XML Schema conformance" is enabled, resulting in this error message. In the XSD schema preference, uncheck the preference "Check full XML Schema conformance" and validate the file. The error should disappear.