TS 70 XML

XML Tools Test Specification for NetBeans 7.0 (6.9)

Contact: Michael A. Nazarov
Version: 1.01
Last update: Mar 2, 2009
Introduction:
Comments: Requires "XML and Schema" plugin installed

Contents 1 XML Tools Test Specification for NetBeans 7.0 (6.9) 1.1 Test suite: Schema Aware Code Completion 1.2 Test suite: XML Document and Schema Generation (todo) 1.3 Test suite: DTD Node Actions (todo) 1.4 Test suite: "All" component 1.5 Test suite: "Any" component 1.6 Test suite: "Any attribute" component 1.7 Test suite: "Global Element" component (todo) 1.8 Test suite: "Global Complex Type" component (todo) 1.9 Test suite: "Global Simple Type" component 1.10 Test suite: "Global Attribute" component 1.11 Test suite: Schema View Editor Window (todo) 1.12 Test suite: Schema View Search 1.13 Test suite: Schema View Refactoring (todo) 1.14 Test suite: Design View Palette (todo) 1.15 Test suite: Design View Keyboard/Icon (todo) 1.16 Test suite: Source View Editor (todo) 1.17 Test suite: Source View Context Menu (todo) 1.18 Test suite: Apply Design Pattern 1.19 Test suite: Schema Retriever Wizard (todo) 1.20 Test suite: Query 1.21 Test suite: Navigator

Test suite: Schema Aware Code Completion

Purpose: Verify Code Completion functionality for multiple scenarios
Setup: Create a new Java Project for these tests

1. From local schema #1
   1. Choose File->New File->XML->Purchase Order Sample Schema, next, finish
   2. Choose File->New File->XML->XML Document, next, XML Schema-Constrained Document
   3. Select Browse in the wizard and navigate to the Purchase Order schema under "By File"
   4. Set the root element to purchaseOrder, next, finish
   5. In the XML document start a tag ("<")
   • EXPECTED RESULT: code completion should give you suggestions
2. From local schema #2
   1. Repeat steps above but at step #3 find the schema under "By Namespace"
   • EXPECTED RESULT: code completion should give you suggestions
3. From local schema #3
   1. Choose File->Java->Java Package, next, finish
   2. Choose File->New File->XML->Purchase Order Sample Schema, next
   3. For the folder field select browse and choose the new package, finish
   4. Choose File->New File->XML->XML Document, Make sure to select a different folder than the Purchase Order was created in for
   5. next, XML Schema-Constrained Document
   6. Select Browse in the wizard and navigate to the Purchase Order schema under "By File"
   7. Set the root element to purchaseOrder, next, finish
   8. In the XML document start a tag ("<")
   • EXPECTED RESULT: code completion should give you suggestions
4. From local schema #4
   1. Repeat steps above but at step #6 find the schema under "By Namespace"
   • EXPECTED RESULT: code completion should give you suggestions
5. From remote (internet) schema
   1. File->New File->XML->XML Document, next, XML Schema-Constrained Document
   2. In the Schema column use the URL: http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
   3. Set the root to Bean once the schema has been retrieved
   4. In the document just above "</ns1:bean>" begin a new tag
   • EXPECTED RESULT: Code Completion should offer suggestions
6. From multiple schemas (wildcards) #1
   1. File->New File->XML->XML Schema accept all defaults
   2. Switch the editor view to Design View
   3. Add an Element to the schema accepting default values
   4. To this element add a few child elements
   5. Switch to source view and just before the first child element declaration add "<xsd:any/>"
   6. Repeat steps 1-4
   7. Choose File->New File->XML->XML Document, next, XML Schema-Constrained Document
   8. Select Browse in the wizard and select the two schemes created under "By File"
   9. Begin a tag in the new XML document and select the top element of the first schema from Suggestions
   • EXPECTED RESULT: Suggestions from all schemas referenced are available
7. From multiple schemas (wildcards) #2
   1. With the same setup as wilcards test #1
   2. Begin a new tag
   3. Select an element from the second schema created and its closing tag as well
   4. Inside of this tag start a new tag
   • EXPECTED RESULT: Suggestions from only the second referenced schema are available
8. From catalog DTD
   1. File->New File->XML->XML Schema, next
   2. Choose DTD-Constrained document, next
   3. Accept all default values, finish
   4. At the end of the document start a new tag
   • EXPECTED RESULT: code completion should offer suggestions from the DTD
9. From catalog Schema
   1. File->New File->Persistence->Persistence Unit, next
   2. Choose a Database Connection, finish
   3. Switch to XML view for persistence.xml
   4. Just above "</persistence>" at the end of the document begin a new tag
   • EXPECTED RESULT: Code Completion offers suggestion

Test suite: XML Document and Schema Generation (todo)

1. Sample XML generation from schema via context menu
   1. Create new loan application sample schema
   2. Right click loan application schema in projects window
   3. select "Generate Sample XML"
   4. accept defaults
   5. run check xml on the XML file
   • EXPECTED RESULT: XML file for is generated, populated with correct information, and is valid
2. Sample XML generation from schema via new file wizard
   1. Create new loan application sample schema
   2. Choose File->New File->XML->XML Document, next
   3. Select XML Schema-Constrained Document, next
   4. Select browse and navigate to the sample schema and set as primary, next, finish
   5. run check xml on the XML file
   • EXPECTED RESULT: XML file for is generated, populated with correct information
3. XML instance generation from a web source
   1. Choose File->New File->XML->XML Document, next
   2. Select XML Schema-Constrained Document, next
   3. Enter a URL for a schema file on the web, ie. http://www.openlaszlo.org/lps/tools/lzx.xsd
   4. Once schema is laoded, set as primary and choose root element, next , finish
   5. run check xml on the XML file
   • EXPECTED RESULT: XML file is generated
4. Multiple XML Schema generation from local sources
   1. Choose File->New File->XML->External XML Schema Document(s), next
   2. Select from local file system, browse
   3. Choose 2 or more schema from filesystem, open, finish
   • EXPECTED RESULT: all selected schema are added to current project
5. XML document creation from multiple schemas (Updated)
   1. File->New File->XML->XML Schema accept all defaults
   2. Add a new Element named "A"
   3. Repeat step 1 to create a second schema
   4. Add a new Element "B"
   5. Choose File->New File->XML->XML Document, next, XML Schema-Constrained Document
   6. Select Browse in the wizard and select the two schemes created under "By File"
   7. set one as primary and complete the wizard
   • EXPECTED RESULT: XML file is generated, schemalocation attribute includes all selected schema

Test suite: DTD Node Actions (todo)

Purpose: Test available DTD actions
Setup: Create a new Java Project, add the Purchase Order Sample Schema, Generate Sample XML of purchase order schema selecting purchaseOrder as the root element, Generate DTD of the xml document

1. Generate CSS
   1. Right click Generated DTD Node in projects view
   2. from the context menu select "Generate CSS..."
   • EXPECTED RESULT: stylesheet for the DTD is generated and is valid
2. Check DTD
   1. Right click Generated DTD Node in projects view
   2. from the context menu select "Check DTD"
   • EXPECTED RESULT: Output Window shows DTD checking Started and DTD Checking finished
3. Generate Documentation
   1. Right click Generated DTD Node in projects view
   2. from the context menu select "Generate Documentation..."
   3. If the file did not open in a browser, manually do this and check documentation created successfully
   • EXPECTED RESULT: html documentation file will be generated and be correct
4. Generate DOM Tree Scanner
   1. Right click Generated DTD Node in projects view
   2. from the context menu select "Generate DOM Tree Scanner..."
   3. check generated file for correctness and contains no errors
   • EXPECTED RESULT: scanner for the DOM tree is generated
5. SAX Document Handler Wizard Sanity
   1. Right click Generated DTD Node in projects view
   2. From the context menu select "SAX Document Handler Wizard"
   3. Accept Defaults, next
   4. For all handler types that are empty, change to ignore, next, next,finish
   • EXPECTED RESULT: 4 files are generated; NewPurchaseOrderHandler.java, NewPurchaseOrderHandlerImpl.java, NewPurchaseOrderParser.java, NewPurchaseOrderSAXBindings
6. SAX Document Handler Wizard Detail
   1. Repeat testcase SAX Document Handler Wizard Sanity with all combinations of JAXP & SAX versions as well as Propagate SAX Events to Generated Handler and save custom bindings options of the wizard
   • EXPECTED RESULT: same results as SAX Document Handler Sanity test case except if save custom bindings is not selected only 3 files will be generated

Test suite: "All" component

Purpose: Checking compliance of "All" component properties and functionality bound up with them
Setup: Select "http://sample.namespace.org|ComplexType-0 (Global Complex Type)|all (All)" path in Explore tree

1. Checking property set
   1. Check properties displayed in Properties pane.
   • EXPECTED RESULT: There should be the following properties available: kind: All, ID: null, Min Occurs: 1.
2. Checking ID property (updated)
   1. Change value of ID to "qwerty".
   • EXPECTED RESULT: It should be possible to do. New value should be displayed on the right of ID.
   1. Change value of ID to "12345".
   • EXPECTED RESULT: Ivalid value should be reported.
   1. Change value of ID to "asdfg".
   • EXPECTED RESULT: It should be possible to do. New value should be displayed on the right of ID.
3. Checking MinOccurs property (updated)
   1. Drop down list of possible MinOccurs values.
   • EXPECTED RESULT: Possible values of MinOccurs are 0 and 1.
   1. Change value of MinOccurs to 0.
   • EXPECTED RESULT: It should be possible to do. New value should be displayed on the right of MinOccurs.
   1. Change value of MinOccurs back to 1.
   • EXPECTED RESULT: It should be possible to do. Old value should be displayed on the right of MinOccurs.
4. Checking updated source
   1. Invoke Go To Source popup menu command on all (All) node.
   • {{{1}}}

Test suite: "Any" component

Purpose: Checking compliance of "Any" component properties and functionality bound up with them
Setup: Select "http://sample.namespace.org|Group-0 (Global Group)|sequence|any (Any)" path in Explore tree

1. Checking property set
   1. Check properties displayed in Properties pane.
   • EXPECTED RESULT: There should be the following properties available: kind: Any, ID: null, Max Occurs: unbounded, Min Occurs: 1, Process Contents: Default for schema (not set). Not yet implemented: Namespace.
2. Checking ID property (updated)
   1. Change value of ID to "qwer".
   • EXPECTED RESULT: It should be possible to do. New value should be displayed on the right of ID.
   1. Change value of ID to "1234".
   • EXPECTED RESULT: Ivalid value should be reported.
   1. Change value of ID to "asdf".
   • EXPECTED RESULT: It should be possible to do. New value should be displayed on the right of ID.
3. Checking MaxOccurs property (updated)
   1. Drop down list of MaxOccurs values.
   • EXPECTED RESULT: Dropped list should contain only value of "unbounded".
   1. Change value of MaxOccurs to *.
   • EXPECTED RESULT: It should be possible to do. "unbounded" value should be displayed on the right of MaxOccurs
   1. Change MaxOccurs property to -5.
   • EXPECTED RESULT: It shouldn't be possible to do.
   1. Change MaxOccurs property to 5.
   • EXPECTED RESULT: New value 5 should be displayed on the right of MaxOccurs
   1. Change value of MaxOccurs to "unbounded".
   • EXPECTED RESULT: "unbounded" value should be displayed on the right of MaxOccurs
   1. Change MaxOccurs property to 2.
   • EXPECTED RESULT: New value 2 should be displayed on the right of MaxOccurs
4. Checking MinOccurs property (updated)
   1. Change MinOccurs property to -5.
   • EXPECTED RESULT: It shouldn't be possible to do.
   1. Change MinOccurs property to 5.
   • EXPECTED RESULT: New value 5 should be displayed on the right of MinOccurs
   1. Change value of MinOccurs to 0.
   • EXPECTED RESULT: New value 0 should be displayed on the right of MinOccurs
5. Checking Process Contents property (updated)
   1. Drop down list of Process Contents values.
   • EXPECTED RESULT: Possible values of Process Contents are as follows: Default for schema (not set), Lax, Skip, Strict.
   1. Change value of Process Contents to Lax.
   • EXPECTED RESULT: Lax value should be displayed on the right of Process Contents
   1. Change value of Process Contents to Skip.
   • EXPECTED RESULT: Skip value should be displayed on the right of Process Contents
   1. Change value of Process Contents to Strict.
   • EXPECTED RESULT: Strict value should be displayed on the right of Process Contents
6. Checking Namespace property (TBD)
7. Checking updated source
   1. Invoke Go To Source popup menu command on all (All) node.
   • {{{1}}}

Test suite: "Any attribute" component

Purpose: Checking compliance of "Any attribute" component properties and functionality bound up with them
Setup: Select "http://sample.namespace.org|AttributeGroup-0 (Global Attribute Group)|anyAttribute (Any Attribute)" path in Explore tree

1. Checking property set
   1. Check properties displayed in Properties pane.
   • EXPECTED RESULT: There should be the following properties available: kind: Any, ID: null, Max Occurs: unbounded, Min Occurs: 1, Process Contents: Default for schema (not set). Not yet implemented: Namespace.
2. Checking ID property (updated)
   1. Change value of ID to "qwer".
   • EXPECTED RESULT: It should be possible to do. New value should be displayed on the right of ID.
   1. Change value of ID to "1234".
   • EXPECTED RESULT: Ivalid value should be reported.
   1. Change value of ID to "asdf".
   • EXPECTED RESULT: It should be possible to do. New value should be displayed on the right of ID.
3. Checking MaxOccurs property (updated)
   1. Drop down list of MaxOccurs values.
   • EXPECTED RESULT: Dropped list should contain only value of "unbounded".
   1. Change value of MaxOccurs to *.
   • EXPECTED RESULT: It should be possible to do. "unbounded" value should be displayed on the right of MaxOccurs
   1. Change MaxOccurs property to -5.
   • EXPECTED RESULT: It shouldn't be possible to do.
   1. Change MaxOccurs property to 5.
   • EXPECTED RESULT: New value 5 should be displayed on the right of MaxOccurs
   1. Change value of MaxOccurs to "unbounded".
   • EXPECTED RESULT: "unbounded" value should be displayed on the right of MaxOccurs
   1. Change MaxOccurs property to 2.
   • EXPECTED RESULT: New value 2 should be displayed on the right of MaxOccurs
4. Checking MinOccurs property (updated)
   1. Change MinOccurs property to -5.
   • EXPECTED RESULT: It shouldn't be possible to do.
   1. Change MinOccurs property to 5.
   • EXPECTED RESULT: New value 5 should be displayed on the right of MinOccurs
   1. Change value of MinOccurs to 0.
   • EXPECTED RESULT: New value 0 should be displayed on the right of MinOccurs
5. Checking Process Contents property (updated)
   1. Drop down list of Process Contents values.
   • EXPECTED RESULT: Possible values of Process Contents are as follows: Default for schema (not set), Lax, Skip, Strict.
   1. Change value of Process Contents to Lax.
   • EXPECTED RESULT: Lax value should be displayed on the right of Process Contents
   1. Change value of Process Contents to Skip.
   • EXPECTED RESULT: Skip value should be displayed on the right of Process Contents
   1. Change value of Process Contents to Strict.
   • EXPECTED RESULT: Strict value should be displayed on the right of Process Contents
6. Checking Namespace property (TBD)
7. Checking updated source
   1. Invoke Go To Source popup menu command on all (All) node.
   • {{{1}}}

Test suite: "Global Element" component (todo)

Purpose: Checking Editing "Global Element" Properties and It's Interaction with Properties Sheet
Setup: Find Global Element "Element-1" in Source.

1. Checking "ID" Property
   1. Add ' id="qwerty" ' to Element-1 in Source.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Id "qwerty" should be displayed for Element in Properties Window.
   1. Switch back to Source View and change id from "qwerty" to "12345".
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.
   1. Switch back to Source View and delete ' id="12345" ' from Element-1.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Value should be empty for ID in Properties Window.
2. Checking "Name" Property
   1. Change Element-1 Name to "Element-12345" in Source.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Name "Element-12345" should be displayed in Properties Window.
   1. Switch back to Source View and change Name to "12345".
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.
   1. Switch back to Source View and change Name back to "Element-1".
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Name "Element-1" should be displayed in Properties Window.
3. Checking "Abstract" Property
   1. Add ' abstract="true" ' to Element-1 in Source.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Value "true" should be displayed for Abstract in Properties Window.
   1. Switch back to Source View and change Abstract to "true" to "true12345".
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.
   1. Switch back to Source View and change Abstract from "true12345" to "false".
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Value "false" should be displayed for Abstract in Properties Window.
   1. Switch back to Source View and delete ' abstract="false" ' from Element-1.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Abstract in Properties Window.
4. Checking "Nillable" Property
   1. Add ' nillable="true" ' to Element-1 in Source.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Value "true" should be displayed for Nillable in Properties Window.
   1. Switch back to Source View and change Nillable to "true" to "true12345".
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.
   1. Switch back to Source View and change Nillable from "true12345" to "false".
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Value "false" should be displayed for Nillable in Properties Window.
   1. Switch back to Source View and delete ' nillable="false" ' from Element-1.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Nillable in Properties Window.
5. Checking "Fixed Value" Property
   1. Add ' fixed="12345" ' to Element-1 in Source.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.

1. • EXPECTED RESULT: Value "12345" should be displayed for Fixed Value in Properties Window.
   1. Switch back to Source View and change Fixed from "12345" to "qwerty".
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Value "qwerty" should be displayed for Fixed Value in Properties Window.
   1. Switch back to Source. Add ' default="12345" ' to Element-1.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.
   1. Switch back to Source View and delete ' default="12345" ' from Element-1.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Default Value in Properties Window.
   1. Switch back to Source View and delete ' fixed="12345" ' from Element-1.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Fixed Value in Properties Window.
2. Checking "Default Value" Property
   1. Add ' default="12345" ' to Element-1 in Source.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.

1. • EXPECTED RESULT: Value "12345" should be displayed for Default Value in Properties Window.
   1. Switch back to Source. Add ' fixed="12345" ' to Element-1.
   • EXPECTED RESULT: It should be possible to do.
   1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and delete ' fixed="12345" ' from Element-1.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Default Value in Properties Window.

1. 1. Switch back to Source View and change Default from "12345" to "qwerty".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "qwerty" should be displayed for Default Value in Properties Window.

1. 1. Switch back to Source View and delete ' default="12345" ' from Element-1.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Default Value in Properties Window.

1. Checking "Prohibited Derivations (Final)" Property

1. 1. Add ' final="#all" ' to Element-1 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "#all" should be displayed for Prohibited Derivations in Properties Window.

1. 1. Click on "Prohibited Derivations (Final)" input field to open dialog.
   • EXPECTED RESULT: "Global element - Prohibited Derivations (Final)" opens. "Prevent all types derivations (#all)" should be selected.

1. 1. Switch back to Source View and change Final from "#all" to "extension restriction".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "extension restriction" should be displayed for Prohibited Derivations in Properties Window.

1. 1. Click on "Prohibited Derivations (Final)" input field to open dialog.
   • EXPECTED RESULT: "Global element - Prohibited Derivations (Final)" opens. "Prevent types derivations of following kinds:" should be selected and Restriction and Extension should be checked.

1. 1. Switch back to Source View and delete ' final="extension restriction" ' from Element-1.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: "Prohibited Derivations (Final)" Value field should be empty in Properties Window.

1. Checking "Prohibited Substitutions (Block)" Property

1. 1. Add ' block="#all" ' to Element-1 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "#all" should be displayed for Prohibited Substitution in Properties Window.

1. 1. Click on "Prohibited Substitutions (Block)" input field to open dialog.
   • EXPECTED RESULT: "Global element - Prohibited Substitutions (Block)" opens. "Block all Substitution (#all)" should be selected.

1. 1. Switch back to Source View and change Block from "#all" to "restriction substitution extension".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "restriction substitution extension" should be displayed for Prohibited Derivations in Properties Window.

1. 1. Click on "Prohibited Substitutions (Block)" input field to open dialog.
   • EXPECTED RESULT: "Global element - Prohibited Substitutions (Block)" opens. "Block Substitutions of following kinds:" should be selected and Restriction, Substitution and Extension should be checked.

1. 1. Switch back to Source View and delete ' block="extension substitution restriction" ' from Element-1.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: "Prohibited Substitutions (Block)" Value field should be empty in Properties Window.

1. Checking "Substitution Group" Property //in revision

Test suite: "Global Complex Type" component (todo)

Purpose: Checking Editing "Global Complex Type" Properties and It's Interaction with Properties Sheet
Setup: Find Global Complex Type "ComplexType-0" in Source.

1. Checking "ID" Property

1. 1. Add ' id="qwerty" ' to ComplexType-0 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Id "qwerty" should be displayed for Element in Properties Window.

1. 1. Switch back to Source View and change id from "qwerty" to "12345".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and delete ' id="12345" ' from ComplexType-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value should be empty for ID in Properties Window.

1. Checking "Name" Property

1. 1. Change ComplexType-0 Name to "ComplexType-012345" in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Name "ComplexType-012345" should be displayed in Properties Window.

1. 1. Switch back to Source View and change Name to "12345".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and change Name back to "ComplexType-0".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Name "ComplexType-0" should be displayed in Properties Window.

1. Checking "Abstract" Property

1. 1. Add ' abstract="true" ' to ComplexType-0 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "true" should be displayed for Abstract in Properties Window.

1. 1. Switch back to Source View and change Abstract to "true" to "true12345".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and change Abstract from "true12345" to "false".

1. • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "false" should be displayed for Abstract in Properties Window.

1. 1. Switch back to Source View and delete ' abstract="false" ' from ComplexType-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Abstract in Properties Window.

1. Checking "Mixed Content" Property

1. 1. Add ' mixed="true" ' to ComplexType-0 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "true" should be displayed for Mixed Content in Properties Window.

1. 1. Switch back to Source View and change Mixed to "true" to "true12345".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and change Mixed from "true12345" to "false".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "false" should be displayed for Mixed Content in Properties Window.

1. 1. Switch back to Source View and delete ' mixed="false" ' from ComplexType-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Mixed Content in Properties Window.

1. Checking "Prohibited Derivations (Final)" Property

1. 1. Add ' final="#all" ' to ComplexType-0 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "#all" should be displayed for Prohibited Derivations in Properties Window.

1. 1. Click on "Prohibited Derivations (Final)" input field to open dialog.
   • EXPECTED RESULT: "Global element - Prohibited Derivations (Final)" opens. "Prevent all types derivations (#all)" should be selected.

1. 1. Switch back to Source View and change Final from "#all" to "extension restriction".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "extension restriction" should be displayed for Prohibited Derivations in Properties Window.

1. 1. Click on "Prohibited Derivations (Final)" input field to open dialog.
   • EXPECTED RESULT: "Global element - Prohibited Derivations (Final)" opens. "Prevent types derivations of following kinds:" should be selected and Restriction and Extension should be checked.

1. 1. Switch back to Source View and delete ' final="extension restriction" ' from ComplexType-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: "Prohibited Derivations (Final)" Value field should be empty in Properties Window.

1. Checking "Prohibited Substitutions (Block)" Property

1. 1. Add ' block="#all" ' to ComplexType-0 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "#all" should be displayed for Prohibited Substitution in Properties Window.

1. 1. Click on "Prohibited Substitutions (Block)" input field to open dialog.
   • EXPECTED RESULT: "Global element - Prohibited Substitutions (Block)" opens. "Block all Substitution (#all)" should be selected.

1. 1. Switch back to Source View and change Block from "#all" to "restriction substitution extension".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "restriction substitution extension" should be displayed for Prohibited Derivations in Properties Window.

1. 1. Click on "Prohibited Substitutions (Block)" input field to open dialog.
   • EXPECTED RESULT: "Global element - Prohibited Substitutions (Block)" opens. "Block Substitutions of following kinds:" should be selected and Restriction, Substitution and Extension should be checked.

1. 1. Switch back to Source View and delete ' block="extension substitution restriction" ' ComplexType-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: "Prohibited Substitutions (Block)" Value field should be empty in Properties Window.

Test suite: "Global Simple Type" component

Purpose: Checking Editing "Global Simple Type" Properties and It's Interaction with Properties Sheet
Setup: Find Global Simple Type "SimpleType-0" in Source.

1. Checking "ID" Property

1. 1. Add ' id="qwerty" ' to SimpleType-0 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Id "qwerty" should be displayed for ID in Properties Window.

1. 1. Switch back to Source View and change id from "qwerty" to "12345".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and delete ' id="12345" ' from SimpleType-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value should be empty for ID in Properties Window.

1. Checking "Name" Property

1. 1. Change SimpleType-0 Name to "SimpleType-012345" in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Name "SimpleType-012345" should be displayed in Properties Window.

1. 1. Switch back to Source View and change Name to "12345".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and change Name back to "SimpleType-0".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Name "SimpleType-0" should be displayed in Properties Window.

1. Checking "Prohibited Derivations (Final)" Property

1. 1. Add ' final="#all" ' to SimpleType-0 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "#all" should be displayed for Prohibited Derivations in Properties Window.

1. 1. Click on "Prohibited Derivations (Final)" input field to open dialog.
   • EXPECTED RESULT: "Global element - Prohibited Derivations (Final)" opens. "Prevent all types derivations (#all)" should be selected.

1. 1. Switch back to Source View and change Final from "#all" to "extension restriction".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "extension restriction" should be displayed for Prohibited Derivations in Properties Window.

1. 1. Click on "Prohibited Derivations (Final)" input field to open dialog.
   • EXPECTED RESULT: "Global element - Prohibited Derivations (Final)" opens. "Prevent types derivations of following kinds:" should be selected and Restriction and Extension should be checked.

1. 1. Switch back to Source View and delete ' final="extension restriction" ' SimpleType-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: "Prohibited Derivations (Final)" Value field should be empty in Properties Window.

Test suite: "Global Attribute" component

Purpose: Checking Editing "Global Attribute" Properties and It's Interaction with Properties Sheet
Setup: Attribute "Attribute-0" in Source.

1. Checking "ID" Property

1. 1. Add ' id="qwerty" ' to Attribute-0 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Id "qwerty" should be displayed for Element in Properties Window.

1. 1. Switch back to Source View and change id from "qwerty" to "12345".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and delete ' id="12345" ' from Attribute-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value should be empty for ID in Properties Window.

1. Checking "Name" Property

1. 1. Change Attribute-0 Name to "Attribute-012345" in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Name "Attribute-012345" should be displayed in Properties Window.

1. 1. Switch back to Source View and change Name to "12345".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and change Name back to "Attribute-0".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Name "Attribute-0" should be displayed in Properties Window.

1. Checking "Fixed Value" Property

1. 1. Add ' fixed="12345" ' to Attribute-0 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "12345" should be displayed for Fixed Value in Properties Window.

1. 1. Switch back to Source View and change Fixed from "12345" to "qwerty".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "qwerty" should be displayed for Fixed Value in Properties Window.

1. 1. Switch back to Source. Add ' default="12345" ' to Attribute-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and delete ' default="12345" ' from Attribute-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Default Value in Properties Window.

1. 1. Switch back to Source View and delete ' fixed="12345" ' from Attribute-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Fixed Value in Properties Window.

1. Checking "Default Value" Property

1. 1. Add ' default="12345" ' to Attribute-0 in Source.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "12345" should be displayed for Default Value in Properties Window.

1. 1. Switch back to Source. Add ' fixed="12345" ' to Attribute-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.

1. • EXPECTED RESULT: Invalid value should be reported.

1. 1. Switch back to Source View and delete ' fixed="12345" ' from Attribute-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Default Value in Properties Window.

1. 1. Switch back to Source View and change Default from "12345" to "qwerty".
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "qwerty" should be displayed for Default Value in Properties Window.

1. 1. Switch back to Source View and delete ' default="12345" ' from Attribute-0.
   • EXPECTED RESULT: It should be possible to do.

1. 1. Switch to Schema View.
   • EXPECTED RESULT: Value "False(non set)" should be displayed for Default Value in Properties Window.

Test suite: Schema View Editor Window (todo)

Purpose: Test functionality of operations available in the Schema View

1. Adding Components
   1. Choose File->New File->XML->Schema, next, finish
   2. Right click Attributes node
   3. Select Add Attribute...
   4. accept defaults
   5. Repeat procedure adding instances of the rest of the component types (Attribute Groups through Simple Types)
   • EXPECTED RESULT: The new component should be added to the schema
2. Import Schema
   1. Create a new schema (Choose File->New File->XML->Schema)
   2. Repeat to generate a second schema
   3. Switch to the first schema in the editor
   4. Right click the Referenced Schema node
   5. Select import
   6. Navigate via By File to the the second schema just created and mark the checkbox next to it
   7. Press OK
   • EXPECTED RESULT: There should be a reference to the second schema from the first
3. Include Schema
   1. Create a new schema (Choose File->New File->XML->Schema)
   2. Repeat, for this second schema, clear the namespace field
   3. Switch to the first schema in the editor
   4. Right click the Referenced Schema node
   5. Select Include
   6. Navigate via By File to the the second schema just created and mark the checkbox next to it
   7. Press OK
   • EXPECTED RESULT: There should be a reference to the second schema from the first
4. Redefine Schema
   1. Create a new schema (Choose File->New File->XML->Schema)
   2. Repeat, for this second schema, clear the namespace field
   3. Switch to the first schema in the editor
   4. Right click the Referenced Schema node
   5. Select Redefine
   6. Navigate via By File to the the second schema just created and mark the checkbox next to it
   7. Press OK
   • EXPECTED RESULT: There should be a reference to the second schema from the first
5. Import External Schema
   1. Create a new schema (Choose File->New File->XML->Schema, next, finish)
   2. switch to source view
   3. add an import to a remote schema as the liast attribute of the schema tag.
   4. ie. <xsd:import schemaLocation="http://schemas.xmlsoap.org/wsdl" namespace="http://schemas.xmlsoap.org/wsdl"/>
   5. Switch back to schema view
   6. Expand Referenced Schemas
   • EXPECTED RESULT: There should be a reference to the external schema
6. Modify Attributes of each instance via Properties
   1. If the properties window is not open do so now
   2. Select newAttribute under the Attributs node
   3. In the name field of the properties window rename newAttribute
   • EXPECTED RESULT: newAttribute should be renamed and reflected across all views
   1. Repeat renaming procedure for all nodes (excluding Referenced Schemas)
   • EXPECTED RESULT: each item should be renamed and reflected across all views
   1. For schema root node change one or more attributes in the properties window
   • EXPECTED RESULT: each change should be reflected across all views
7. Modify Attributes of each instance via Customizer
   1. Add an instance of each type of component (excluding Referenced Schema) to a new XML document
   2. Use Customizer (where applicable) for all items via right click on item
   • EXPECTED RESULT: customization should be reflected for each item customized and reflected across all views
8. Navigate Through Schema
   1. Create Loan Sample Schema (NewFIle->XML->Loan Application Sample Schema)
   2. Navigate through column representation of schema (Column View)
   3. Navigate through tree representation of schema (Tree View)
   • EXPECTED RESULT: all nodes/items should be reachable
9. Check and Validate Schema
   1. Create Loan Sample Schema (NewFIle->XML->Loan Application Sample Schema)
   2. Select Validate schema from window menu bar
   • EXPECTED RESULT: schema is valid
10. Syncronization Between Views
    1. Create Loan Sample Schema (NewFIle->XML->Loan Application Sample Schema)
    2. Clone the schema 3 times
    3. Switch each cloned window to a different view (schema, design, source)
    4. Tile the windows so each are visible
    5. For each view have visible in the window the element Loan from autoLoanApplication element
    6. modify the name "Loan" to some other name in schema view/properties Name field.
    • EXPECTED RESULT: All views should keep in sync (have the new name)
11. GoTo Source/Design
    1. Create Loan Sample Schema (NewFIle->XML->Loan Application Sample Schema)
    2. In schema view expand the Complex Types node
    3. Right click AddressType and select GoTo->source
    • EXPECTED RESULT: View changes to Source view and AddressType is selected
    1. Repeat this time selecting GoTo->Design
    • EXPECTED RESULT: View changes to design view and AddressType is selected
12. Deletion of Components
    1. Create a new schema
    2. Add a new instance of each component type
    3. Delete each new instance
    • EXPECTED RESULT: item is removed all views remain in sync

Test suite: Schema View Search

Purpose: Test functionality of search in the Schema View

1. Invoke Search
   1. Invoke search via Ctrl+f and from the Edit menu
   • EXPECTED RESULT: search bar opens at the bottom of the editor window
2. Search for Component Name
   1. Create new loan sample schema
   2. In Column View invoke search via Ctrl+f or from the Edit menu
   3. In the search field enter Address and press return
   • EXPECTED RESULT: 6 occurrences of components with Address in their name are highlighted
   1. Repeat search but in Tree View
   • Expected Result: same as in Column View
3. Navigate Search Results
   1. Create new loan sample schema
   2. Invoke search via Ctrl+f or from the Edit menu
   3. In the search field enter Address and press return
   4. Use the Find Next and Find Previous buttons to navigate through results
   • EXPECTED RESULT: Next cycles one direction through results and Previous cycles the other way
   1. Repeat search navigation but in Tree View
   • Expected Result: same as in Column View
4. Search for Component Kind
   1. Create new loan sample schema
   2. In Column View invoke search via Ctrl+f or from the Edit menu
   3. Change the search type to Component Kind from the search field drop down list
   4. In the search field enter Complex and press return
   • EXPECTED RESULT: 14 occurrences of components of Complex kind are highlighted
   1. Repeat search but in Tree View
   • Expected Result: same as in Column View
5. Search for Attribute Value
   1. Create new loan sample schema
   2. In Column View invoke search via Ctrl+f or from the Edit menu
   3. Change the search type to Attribute Value from the search field drop down list
   4. In the search field enter loan and press return
   • EXPECTED RESULT: 4 occurrences are found
   1. Repeat search but in Tree View
   • Expected Result: same as in Column View
6. Search from selected
   1. Create new loan sample schema
   2. In Column View invoke search via Ctrl+f or from the Edit menu
   3. Navigate to Complex Types->AddressType and click sequence
   4. Using the drop down in the search bar select Search Selection
   5. In search box enter address press return
   • EXPECTED RESULT: 2 occurrence are found
   1. Repeat search but in Tree View

1. • Expected Result: same as in Column View
2. Search for non existent component
   1. Create new loan sample schema
   2. In Column View invoke search via Ctrl+f or from the Edit menu
   3. In search box enter new press return
   • EXPECTED RESULT: No occurrence are found textbox becomes red
   1. Repeat search but in Tree View
   • Expected Result: same as in Column View
3. Invoke Advanced Search
   1. In Column View invoke advanced search via menu icon (binoculars)
   • EXPECTED RESULT: Advanced Search Window appears
   1. Repeat search but in Tree View
   • Expected Result: same as in Column View
4. Invoke Advanced Search
   1. Create Loan Application Sample Schema
   2. In Column View invoke advanced search via menu icon
   3. Change the Target field to Complex Type
   4. Change Name field to Address* and search
   • EXPECTED RESULT: Advanced Search output pane opens showing 1 occurrence
   1. Repeat search but in Tree View
   • Expected Result: same as in Column View
5. Find Usages
   1. Create Loan Application Sample Schema
   2. In Column View right click CarType under Complex Types
   3. Select Find Usages
   • EXPECTED RESULT: Output pane opens showing 1 occurrence with trail from top most node down to occurrence
   1. Repeat search but in Tree View
   • Expected Result: same as in Column View

Test suite: Schema View Refactoring (todo)

Purpose: Test Refactoring in Schema View

1. Rename From Context menu no preview
   1. Create the Purchase Order Schema
   2. Expand Complex Types
   3. Right click Items and select Refactor -> rename
   4. Change the name to something else
   5. Select refactor
   • EXPECTED RESULT: Items is immediately renamed and change is reflected across all views and instances
2. Rename From Context menu with preview
   1. Create the Purchase Order Schema
   2. Expand Complex Types
   3. Right click Items and select Refactor -> rename
   4. Change the name to something else
   5. Select preview
   6. Preview Pane will open showing occurrences and a diff of the source
   7. Select do refactoring in preview pane
   • EXPECTED RESULT: Items is renamed and change is reflected across all views and instances
3. Undo Rename
   1. Create the Purchase Order Schema
   2. Expand Complex Types
   3. Right click Items and select Refactor -> rename
   4. Change the name to something else
   5. Select refactor
   6. Right click the newly renamed type
   7. Select Refactor -> undo rename
   • EXPECTED RESULT: Modified name is reverted back to Items and change is reflected across all views and instances
4. Safe Delete no Preview
   1. Create a new schema
   2. Add a new complex type
   3. Right click the new complex type and select Refactor -> Safe Delete
   4. Select refactor
   • EXPECTED RESULT: The component is deleted and change is reflected across all views
5. Safe Delete with Preview
   1. Create a new schema
   2. Add a new complex type
   3. Right click the new complex type and select Refactor -> Safe Delete
   4. Select preview
   5. Preview Pane will open showing occurrences
   6. Select Do Refactoring in preview pane
   • EXPECTED RESULT: The component is deleted and change is reflected across all views
6. Undo Safe Delete
   1. Create a new schema
   2. Add a new complex type
   3. Right click the new complex type and select Refactor -> Safe Delete
   4. Select refactor
   5. From the Refactor menu item select Undo Delete newComplexType
   • EXPECTED RESULT: The deletion of newComplexType is undone and change is reflected across all views
7. Rename From Refactor menu item no preview
   1. Create the Purchase Order Schema
   2. Expand Complex Types
   3. Select Items
   4. From the menubar select Refactor->Rename
   5. Select refactor
   • EXPECTED RESULT: Items is immediately renamed and change is reflected across all views and instances
8. Rename From Refactor menu item with preview
   1. Create the Purchase Order Schema
   2. Expand Complex Types
   3. Select Items
   4. From the menubar select Refactor->Rename
   5. Change the name to something else
   6. Select preview
   7. Preview Pane will open showing occurrences and a diff of the source
   8. Select do refactoring in preview pane
   • EXPECTED RESULT: Items is renamed and change is reflected across all views and instances
9. Cut/Copy Paste Attributes
   1. Create the Purchase Order Schema
   2. Expand Complex Types
   3. Select PurchaseOrderType
   4. Right click the OrderDate attribute select copy
   5. Right click USAddress Complex Type and choose paste
   6. Delete the just pasted item from USAddressType
   7. Repeat steps 4 & 5 choosing cut instead of copy.
   • EXPECTED RESULT: OrderDate attribute added to USAddress complex type, OrderDate removed from PurchaseOrderType
10. Cut/Copy Paste Components
    1. Create the Purchase Order Schema
    2. Create a new schema
    3. Expand Complex Types of Purchase Order
    4. Right Click PurchaseOrderType select Copy
    5. Switch to new schema right click Complex Types node and select paste
    6. Delete the just pasted item from USAddressType
    7. Repeat steps 4 & 5 choosing cut instead of copy.
    8. EXPECTED RESULT: PurchaseOrderType added to new schema and removed from PurchaseOrder schema
    9. Perform the same copy/cut paste selecting more than one component at once
    • EXPECTED RESULT: several components can be copied/cut pasted at once

Test suite: Design View Palette (todo)

Purpose: Test Palette Items in Design View

1. Palette Element to Schema Node
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   • EXPECTED RESULT: new element added under the Elements node
2. Palette Element to Element Node
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop an Element item from the palette to the elements node
   • EXPECTED RESULT: new element added under the elements node
3. Palette Complex Type to Schema Node
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop a Complex Type item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   • EXPECTED RESULT: new Complex Type added under the Complex Type node
4. Palette Complex Type to Complex Types Node
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop a Complex Type item from the palette to the Complex Types node
   • EXPECTED RESULT: Complex Type to Complex Types Node
5. Palette Attribute to Schema Node
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop a Complex Type item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   4. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   5. Drag and drop an Attribute item from the palette to newElement
   6. Drag and drop an Attribute item from the palette to newComplexType
   • EXPECTED RESULT: newAttribute of type string added to newComplexType and newElement
6. Palette Complex Type Compositors
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop a Complex Type item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   4. Repeat 2 more times
   5. Drag and Drop the item all from the palette onto the first Complex Type
   6. Drag and Drop the item choice from the palette onto the second Complex Type
   7. Drag and Drop the item sequence from the palette onto the third Complex Type
   • EXPECTED RESULT: newComplexType should now be of type all, newComplexType1 should now be of type choice, newComplexType2 should now have be of type sequence

Test suite: Design View Keyboard/Icon (todo)

Purpose: Test Design View Keyboard/Icons

1. Rename via F2
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   4. Select newElement
   5. Press F2
   • EXPECTED RESULT: new element name is now in edit mode
2. Rename via Spacebar
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   4. Select newElement
   5. Press Spacebar
   • EXPECTED RESULT: new element name is now in edit mode
3. Rename via Shift+Click
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   4. Press Shift and Click newElement
   • EXPECTED RESULT: new element name is now in edit mode
4. Undo via keyboard
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   4. Select newElement
   5. Press F2
   6. Rename element
   7. Press enter
   8. Press Ctrl+z
   • EXPECTED RESULT: new element name change is undone
5. Redo via keyboard
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   4. Select newElement
   5. Press F2
   6. Rename element
   7. Press Ctrl+z
   8. Press Ctrl+y
   • EXPECTED RESULT: new element name change is undone then redone
6. Undo via menu
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   4. Select newElement
   5. Press F2
   6. Rename element
   7. Press enter
   8. Press the undo icon in the menu bar
   • EXPECTED RESULT: new element name change is undone
7. Redo via menu
   1. Create a new Schema
   2. Switch to Design View
   3. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
   4. Select newElement
   5. Press F2
   6. Rename element
   7. Press Enter
   8. Press Ctrl+z
   9. Press the redo icon in the menu bar
   • EXPECTED RESULT: new element name change is undone then redone
8. Navigation Drill Down
   1. Create new loan application schema
   2. Switch to Design View
   3. Press the right arrow key to expand each node
   • EXPECTED RESULT: every element and complex type are accessible
9. Navigation Fold Up
   1. Create new loan application schema
   2. Switch to Design View
   3. Press the right arrow key to expand each node until all nodes are fully expanded
   4. Press the left arrow key to collapse each node untill all nodes are colapsed
   • EXPECTED RESULT: Design View shows only top most components
10. Add Element via Keyboard
    1. Create a new Schema
    2. Switch to Design View
    3. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
    4. Press shift + e
    5. Press return
    • EXPECTED RESULT: A new child element is born
11. Add Attribute via Keyboard
    1. Create a new Schema
    2. Switch to Design View
    3. Drag and drop an Element item from the palette to the schema top node (http://xml.netbeans.org/schema/newXMLSchema)
    4. Press shift+e
    5. Press enter
    6. press shift+a
    7. enter again
    • EXPECTED RESULT: A new child element is born and a new attribute is added to the newborn

Test suite: Source View Editor (todo)

Purpose: Test Source View Editor features/functionality

1. Editor Window Find/Navigate/Toggle Search
   1. Create a new Schema
   2. Switch to Source View
   3. EXPECTED RESULT: XML structure should be neatly formatted and editable
   4. Highlight the word "schema"
   5. From the Editor Window Menu bar select find selection
   6. EXPECTED RESULT: All instances of the text "schema" are highlighted

1. 1. Using the Find Previous and Find Next menu items cycle through selected items
   2. EXPECTED RESULT: Can go forward and backward through all instances of selected text
   3. Select the Toggle Highlight Search icon in the editor's menu bar
   • EXPECTED RESULT: highlighting of selected text is toggled off
2. Bookmarks/Bookmark Navigation
   1. Create a new Schema
   2. Switch to Source View
   3. Place cursor at line 3
   4. Click the Toggle Bookmark editor window menu bar item
   5. Place cursor at line 8
   6. Click the Toggle Bookmark editor window menu bar item
   7. Using the bookmark navigation icons cycle back and forth between bookmarks going forward and backward
   • EXPECTED RESULT: Line 3 and 8 are bookmarked and can navigate from one bookmark to the next
3. Selection Indentation
   1. Create a new Schema
   2. Switch to Source View
   3. Highlight a section of code
   4. Using the indent icon in the editor menu window select indent right
   5. Repeat using indent left
   • EXPECTED RESULT: selection is indented with each click of the menu item
4. Check XML
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. click the check xml icon in the menu bar
   • EXPECTED RESULT: output window will open and XML will be check and completed without errors
5. Validate XML
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. click the validate xml icon in the menu bar
   • EXPECTED RESULT: output window will open and XML will be validated, 0 errors 0 warnings
6. XSL Transformation
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. click the XSL Transformation icon in the menu bar
   • EXPECTED RESULT: XSLT wizard will appear

Test suite: Source View Context Menu (todo)

Purpose: Test actions available from the context menu in source view

1. Format Code
   1. Create the Purchase Order Schema
   2. Indent some tags so that they are misaligned and bad form
   3. Right click in the editor window and select Format from the context menu
   • EXPECTED RESULT: The document will have a coherent indentation arrangement and empty lines are removed
2. Check XML
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. Right click in the editor window and select Check XML from the context menu
   • EXPECTED RESULT: output window will open and XML will be check and completed without errors
3. Validate XML
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. Right click in the editor window and select Validate XML from the context menu
   • EXPECTED RESULT: output window will open and XML will be validated, 0 errors 0 warnings
4. XSL Transformation
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. Right click in the editor window and select XSL Transformation from the context menu
   • EXPECTED RESULT: XSLT wizard will appear
5. Cut
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. Highlight some code
   4. Right click in the editor window and select Cut from the context menu
   • EXPECTED RESULT: selected text is removed
6. Paste
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. Highlight some code
   4. Right click in the editor window and select Cut from the context menu
   5. Move the cursor to some other location
   6. Right click in the editor window and select paste from the context menu
   • EXPECTED RESULT: Text cut is pasted at new location
7. Copy
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. Highlight some code
   4. Right click in the editor window and select Copy from the context menu
   5. Move the cursor to some other location
   6. Right click in the editor window and select paste from the context menu
   • EXPECTED RESULT: copied text is pasted at new location
8. Go To Schema
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. Highlight the name of an element
   4. right click selection and choose GoTo -> Schema
   • EXPECTED RESULT: View is changed to Schema View and element selected in source view has focus
9. Go To Design
   1. Create a new loan application sample schema
   2. Switch to Source View
   3. Highlight the name of an element
   4. right click selection and choose GoTo -> Design
   • EXPECTED RESULT: View is changed to Design View
10. Go To Definition
    1. Create a new loan application sample schema
    2. Switch to Source View
    3. Highlight the name of the first element "loan"
    4. right click selection and choose GoTo -> Definition
    • EXPECTED RESULT: Cursor is moved to the location of the definition of type LoanType

Test suite: Apply Design Pattern

Purpose: Abuse the Apply Design Pattern functionality

1. Apply Salami Slice Design Pattern to OTA schema
   1. Create an instance of the OTA schema (attached to this document or from Travel BPEL sample project)
   2. Open the OTA schema
   3. Right Click the schema in the projects window
   4. select Apply Design Pattern
   5. Change to Salami Slice
   • EXPECTED RESULT: After some time, the structure of the document will be salami slice style
2. Apply Design Patterns to Loan Application schema
   1. Create Sample Loan Application
   2. Open the schema
   3. Right Click the schema in the projects window
   4. select Apply Design Pattern
   5. Change to Salami Slice
   6. Validate Schema
   7. Repeat steps 3 & 4 for each other design pattern (Garden of Eden, Russian Doll, Venetian Blind) and validate after each change
   • EXPECTED RESULT: The structure of the document will be style selected schema will be valid

Test suite: Schema Retriever Wizard (todo)

Purpose: Test ability to retrieve external schema

1. From URL
   1. Open the output window
   2. Create a new schema from external schema: New->XML->External Schema Document(s), next
   3. For the URL use http://www.springframework.org/schema/beans/spring-beans-2.5.xsd or other internet schema
   • EXPECTED RESULT: Output window shows schema was retrieved only one time and schema is added to the project
2. From Local Filesystem
   1. Create the BPEL sample project Travel Reservation Service
   2. Create a new BPEL module
   3. Open the output window
   4. To the new BPEL module add a new external schema (New->XML->External Schema Document(s), next)
   5. Select Local Filesystem and chose browse
   6. Browse to OTA.xsd in the TRAVEL Reservation Project
   • EXPECTED RESULT: Output window shows schema was retrieved only one time and copied to current project
3. From Invalid URL
   1. Open the output window
   2. Create a new schema from external schema: New->XML->External Schema Document(s), next
   3. For the URL use http://www.netbeans.org/test.xsd or other invalid internet schema
   • EXPECTED RESULT: Output window shows error: file not found and schema is not added to project
4. From URL to different location
   1. Open the output window
   2. Create a new schema from external schema: New->XML->External Schema Document(s), next
   3. For the URL use http://www.springframework.org/schema/beans/spring-beans-2.5.xsd or other internet schema
   4. Change the save to folder to a different location
   5. finish wizard
   • EXPECTED RESULT: Output window shows schema was retrieved only one time and schema is added to the specified location
5. From Local Filesystem to different location
   1. Open the output window
   2. Create the BPEL sample project Travel Reservation Service
   3. Create a new BPEL module
   4. Open the output window
   5. To the new BPEL module add a new external schema (New->XML->External Schema Document(s), next)
   6. Select Local Filesystem and chose browse
   7. Browse to OTA.xsd in the TRAVEL Reservation Project
   8. Change the save to folder to a different location
   9. finish wizard
   • EXPECTED RESULT: Output window shows schema was retrieved only one time and schema is added to the specified location

Test suite: Query

Purpose: Test different Query actions

1. Find Unused Components 1
   1. Create Purchase Order Sample Schema
   2. In the projects window right click newPurchaseOrder schema
   3. From the context menu select Query->Find Unused Components
   4. Press OK in the wizard
   • EXPECTED RESULT: Output window shows that there is one unused global component
2. Find Unused Components 2
   1. Create Purchase Order Sample Schema
   2. In the projects window right click newPurchaseOrder schema
   3. From the context menu select Query->Find Unused Components
   4. In the wizard mark the Exclude Global Elements check box
   5. Pres OK to finish the wizard
   • EXPECTED RESULT: Output window shows that there were 0 unused global components
3. Find Derivations of Complex Type
   1. Add OTA sample schema to a project
   2. In the projects window right click OTA_TravelItinerary schema
   3. From the context menu select Query->Find Derivations of Complex Type
   4. Select AddressType and press OK
   • EXPECTED RESULT: Output window shows usage map and there are 3 extensions and 0 restrictions
4. Find Substitution Groups
   1. Create a new Schema
   2. Add An element call it E1
   3. Add another element call it Sub
   4. In schema view, select E1
   5. In Properties Window for E1 select Substitution Group
   6. In the wizard select Elemets->Sub and press OK
   7. In the projects window, From the context menu for the schema select Query->Find Substitution Groups
   • EXPECTED RESULT: Output window shows E1 with pointer to Sub

Test suite: Navigator

Purpose: Test different Navigator Actions

1. Design View/Schema View GoTO actions
   1. Create Loan Application Sample Schema
   2. In the Navigator Pane Design View should be selected in the drop down
   3. For any node right click and select GoTo
   4. Choose Source
   5. Repeat Choose Schema
   6. Repeat Choose Design
   7. Change the View Drop Down to Schema View and repeat all 3 GoTo options
   • EXPECTED RESULT: Editor window is changed to selected view selected node is highlighted
2. XML View Show/Hide Attributes
   1. Create Loan Application Sample Schema
   2. In Navigator Pane select XML View
   3. Toggle show hide attributes
   • EXPECTED RESULT: Attributes will be toggled on/off
3. XML View Show/Hide XML Content
   1. Create A new schema
   2. Add some text in the root element
   3. In the navigator pane XML View toggle show hide XML content
   • EXPECTED RESULT: Content added to XML document will be toggled on/off

• This page was last modified on 15 March 2010, at 08:20.
• This page has been accessed 3,265 times.