TS 61 XML

XML Tools Test Specification for NetBeans 6.1

Author: Tony Beckham
Version: 1.3
Last update: 05/21/2008
Introduction:
Comments: Requires "XML and Schema" plugin installed

Contents


Test suite: Schema Aware Code Completion (auto)

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 (auto)

  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
    1. File->New File->XML->XML Schema accept all defaults
    2. Repeat step 1 to create a second schema
    3. Choose File->New File->XML->XML Document, next, XML Schema-Constrained Document
    4. Select Browse in the wizard and select the two schemes created under "By File"
    5. 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 (auto)

Setup:

  1. Create a new Java Project
  2. To this project add the Purchase Order Sample Schema
  3. Generate Sample XML of purchase order schema selecting purchaseOrder as the root element
  4. Generate DTD of the xml document
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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 (auto)

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
    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.
    1. Undo the last changes by pressing Undo toolbar button.
    • EXPECTED RESULT: Value of ID property should be reverted to qwerty.
    1. Redo the last changes by pressing Redo toolbar button.
    • EXPECTED RESULT: Value of ID property should be reverted back to asdfg.
  3. Checking MinOccurs property
    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.
    1. Undo the last changes by pressing Undo toolbar button.
    • EXPECTED RESULT: Value of MinOccurs property should be reverted to 0.
    1. Redo the last changes by pressing Redo toolbar button.
    • EXPECTED RESULT: Value of MinOccurs property should be reverted back to 1.
  4. Checking updated source
    1. Invoke Go To Source popup menu command on all (All) node.
    • {{{1}}}

Test suite: "Any" component (auto)

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
    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.
    1. Undo the last changes by pressing Undo toolbar button.
    • EXPECTED RESULT: Value of ID property should be reverted to qwer.
    1. Redo the last changes by pressing Redo toolbar button.
    • EXPECTED RESULT: Value of ID property should be reverted back to asdf.
  3. Checking MaxOccurs property
    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
    1. Undo the last changes by pressing Undo toolbar button.
    • EXPECTED RESULT: Value of MaxOccurs property should be reverted to "unbounded".
    1. Redo the last changes by pressing Redo toolbar button.
    • EXPECTED RESULT: Value of MaxOccurs property should be reverted back to 2.
  4. Checking MinOccurs property
    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
    1. Undo the last changes by pressing Undo toolbar button.
    • EXPECTED RESULT: Value of MinOccurs property should be reverted to 5.
    1. Redo the last changes by pressing Redo toolbar button.
    • EXPECTED RESULT: Value of MinOccurs property should be reverted back to 0.
  5. Checking Process Contents property
    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
    1. Undo the last changes by pressing Undo toolbar button.
    • EXPECTED RESULT: Value of Process Content property should be reverted to Skip.
    1. Redo the last changes by pressing Redo toolbar button.
    • EXPECTED RESULT: Value of Process Content property should be reverted back to Strict.
  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 (auto)

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
    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.
    1. Undo the last changes by pressing Undo toolbar button.
    • EXPECTED RESULT: Value of ID property should be reverted to qwer.
    1. Redo the last changes by pressing Redo toolbar button.
    • EXPECTED RESULT: Value of ID property should be reverted back to asdf.
  3. Checking MaxOccurs property
    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
    1. Undo the last changes by pressing Undo toolbar button.
    • EXPECTED RESULT: Value of MaxOccurs property should be reverted to "unbounded".
    1. Redo the last changes by pressing Redo toolbar button.
    • EXPECTED RESULT: Value of MaxOccurs property should be reverted back to 2.
  4. Checking MinOccurs property
    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
    1. Undo the last changes by pressing Undo toolbar button.
    • EXPECTED RESULT: Value of MinOccurs property should be reverted to 5.
    1. Redo the last changes by pressing Redo toolbar button.
    • EXPECTED RESULT: Value of MinOccurs property should be reverted back to 0.
  5. Checking Process Contents property
    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
    1. Undo the last changes by pressing Undo toolbar button.
    • EXPECTED RESULT: Value of Process Content property should be reverted to Skip.
    1. Redo the last changes by pressing Redo toolbar button.
    • EXPECTED RESULT: Value of Process Content property should be reverted back to Strict.
  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 (auto)

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 Explore 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 Explore 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 Explore 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 Explore 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 Explore 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 Explore 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 Explore 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 Explore 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 Explore 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 Explore 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 Explore 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 Explore 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 Explore 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 Explore 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 Explore View.
    • 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 Explore 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 Explore 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 Explore 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 Explore View.
    • EXPECTED RESULT: Value "False(non set)" should be displayed for Fixed Value in Properties Window.
  6. Checking "Default Value" Property
    1. Add ' default="12345" ' to Element-1 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • 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 Explore View.
    • EXPECTED RESULT: Invalid value should be reported.
    1. Switch back to Source View and delete ' fixed="12345" ' from Element-1.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "False(non set)" should be displayed for Default Value in Properties Window.
    1. Switch back to Source View and change Default from "12345" to "qwerty".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "qwerty" should be displayed for Default Value in Properties Window.
    1. Switch back to Source View and delete ' default="12345" ' from Element-1.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "False(non set)" should be displayed for Default Value in Properties Window.
  1. Checking "Prohibited Derivations (Final)" Property
    1. Add ' final="#all" ' to Element-1 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "#all" should be displayed for Prohibited Derivations in Properties Window.
    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. Switch back to Source View and change Final from "#all" to "extension restriction".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "extension restriction" should be displayed for Prohibited Derivations in Properties Window.
    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. Switch back to Source View and delete ' final="extension restriction" ' from Element-1.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: "Prohibited Derivations (Final)" Value field should be empty in Properties Window.
  1. Checking "Prohibited Substitutions (Block)" Property
    1. Add ' block="#all" ' to Element-1 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "#all" should be displayed for Prohibited Substitution in Properties Window.
    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. Switch back to Source View and change Block from "#all" to "restriction substitution extension".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "restriction substitution extension" should be displayed for Prohibited Derivations in Properties Window.
    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. Switch back to Source View and delete ' block="extension substitution restriction" ' from Element-1.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: "Prohibited Substitutions (Block)" Value field should be empty in Properties Window.
  1. Checking "Substitution Group" Property
    1. Add ' substitutionGroup="IncludedElement" ' to Element-1 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "IncludedElement" should be displayed for Substitution Group in Properties Window.
    1. Click on "Substitution Group" input field to open dialog.
    • EXPECTED RESULT: "Global element - Substitution Group" opens. "IncludedElement" should be selected.
    1. Switch back to Source View and change Substitution Group from "IncludedElement" to "ImportedElement".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "ImportedElement" should be displayed for Substitution Group in Properties Window.
    1. Click on "Substitution Group" input field to open dialog.
    • EXPECTED RESULT: "Global element - Substitution Group" opens. "ImportedElement" should be selected.
    1. Switch back to Source View and delete ' substitutionGroup="IncludedElement" ' from Element-1.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: "Substitution Group" Value field should be empty in Properties Window.


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

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. Add ' id="qwerty" ' to ComplexType-0 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore 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 Explore View.
    • EXPECTED RESULT: Invalid value should be reported.
    1. Switch back to Source View and delete ' id="12345" ' from ComplexType-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value should be empty for ID in Properties Window.
  1. Checking "Name" Property
    1. Change ComplexType-0 Name to "ComplexType-012345" in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Name "ComplexType-012345" 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 Explore View.
    • EXPECTED RESULT: Invalid value should be reported.
    1. Switch back to Source View and change Name back to "ComplexType-0".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Name "ComplexType-0" should be displayed in Properties Window.
  1. Checking "Abstract" Property
    1. Add ' abstract="true" ' to ComplexType-0 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore 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 Explore 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 Explore View.
    • EXPECTED RESULT: Value "false" should be displayed for Abstract in Properties Window.
    1. Switch back to Source View and delete ' abstract="false" ' from ComplexType-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "False(non set)" should be displayed for Abstract in Properties Window.
  1. Checking "Mixed Content" Property
    1. Add ' mixed="true" ' to ComplexType-0 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "true" should be displayed for Mixed Content in Properties Window.
    1. Switch back to Source View and change Mixed to "true" to "true12345".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Invalid value should be reported.
    1. Switch back to Source View and change Mixed from "true12345" to "false".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "false" should be displayed for Mixed Content in Properties Window.
    1. Switch back to Source View and delete ' mixed="false" ' from ComplexType-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "False(non set)" should be displayed for Mixed Content in Properties Window.
  1. Checking "Prohibited Derivations (Final)" Property
    1. Add ' final="#all" ' to ComplexType-0 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "#all" should be displayed for Prohibited Derivations in Properties Window.
    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. Switch back to Source View and change Final from "#all" to "extension restriction".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "extension restriction" should be displayed for Prohibited Derivations in Properties Window.
    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. Switch back to Source View and delete ' final="extension restriction" ' from ComplexType-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: "Prohibited Derivations (Final)" Value field should be empty in Properties Window.
  1. Checking "Prohibited Substitutions (Block)" Property
    1. Add ' block="#all" ' to ComplexType-0 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "#all" should be displayed for Prohibited Substitution in Properties Window.
    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. Switch back to Source View and change Block from "#all" to "restriction substitution extension".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "restriction substitution extension" should be displayed for Prohibited Derivations in Properties Window.
    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. Switch back to Source View and delete ' block="extension substitution restriction" ' ComplexType-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: "Prohibited Substitutions (Block)" Value field should be empty in Properties Window.


Test suite: "Global Simple Type" component (auto)

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. Add ' id="qwerty" ' to SimpleType-0 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Id "qwerty" should be displayed for ID 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 Explore View.
    • EXPECTED RESULT: Invalid value should be reported.
    1. Switch back to Source View and delete ' id="12345" ' from SimpleType-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value should be empty for ID in Properties Window.
  1. Checking "Name" Property
    1. Change SimpleType-0 Name to "SimpleType-012345" in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Name "SimpleType-012345" 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 Explore View.
    • EXPECTED RESULT: Invalid value should be reported.
    1. Switch back to Source View and change Name back to "SimpleType-0".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Name "SimpleType-0" should be displayed in Properties Window.
  1. Checking "Prohibited Derivations (Final)" Property
    1. Add ' final="#all" ' to SimpleType-0 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "#all" should be displayed for Prohibited Derivations in Properties Window.
    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. Switch back to Source View and change Final from "#all" to "extension restriction".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "extension restriction" should be displayed for Prohibited Derivations in Properties Window.
    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. Switch back to Source View and delete ' final="extension restriction" ' SimpleType-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: "Prohibited Derivations (Final)" Value field should be empty in Properties Window.


Test suite: "Global Attribute" component (auto)

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

  1. Checking "ID" Property
    1. Add ' id="qwerty" ' to Attribute-0 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore 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 Explore View.
    • EXPECTED RESULT: Invalid value should be reported.
    1. Switch back to Source View and delete ' id="12345" ' from Attribute-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value should be empty for ID in Properties Window.
  1. Checking "Name" Property
    1. Change Attribute-0 Name to "Attribute-012345" in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Name "Attribute-012345" 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 Explore View.
    • EXPECTED RESULT: Invalid value should be reported.
    1. Switch back to Source View and change Name back to "Attribute-0".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Name "Attribute-0" should be displayed in Properties Window.
  1. Checking "Fixed Value" Property
    1. Add ' fixed="12345" ' to Attribute-0 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • 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 Explore View.
    • EXPECTED RESULT: Value "qwerty" should be displayed for Fixed Value in Properties Window.
    1. Switch back to Source. Add ' default="12345" ' to Attribute-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Invalid value should be reported.
    1. Switch back to Source View and delete ' default="12345" ' from Attribute-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore 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 Attribute-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "False(non set)" should be displayed for Fixed Value in Properties Window.
  1. Checking "Default Value" Property
    1. Add ' default="12345" ' to Attribute-0 in Source.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "12345" should be displayed for Default Value in Properties Window.
    1. Switch back to Source. Add ' fixed="12345" ' to Attribute-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Invalid value should be reported.
    1. Switch back to Source View and delete ' fixed="12345" ' from Attribute-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "False(non set)" should be displayed for Default Value in Properties Window.
    1. Switch back to Source View and change Default from "12345" to "qwerty".
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "qwerty" should be displayed for Default Value in Properties Window.
    1. Switch back to Source View and delete ' default="12345" ' from Attribute-0.
    • EXPECTED RESULT: It should be possible to do.
    1. Switch to Explore View.
    • EXPECTED RESULT: Value "False(non set)" should be displayed for Default Value in Properties Window.


Test suite: Schema View Editor Window (auto in progress)

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
    • EXPECTED RESULT: newAttribute is added to the schema
    1. Create a new schema (Choose File->New File->XML->Schema, next, give schema a unique name)
    2. The schema should open in the editor
    3. Switch to the first schema
    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
    1. Repeat procedure for the rest of the component types (Attribute Groups through Simple Types)
    • EXPECTED RESULT: The new component should be added to the schema
  2. 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
  3. 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
  4. 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
  5. Check and Validate Schema
    1. Create Loan Sample Schema (NewFIle->XML->Loan Application Sample Schema)
    2. Select Validate schema
    • EXPECTED RESULT: schema is valid
    1. Switch to source view and select check XML
    • EXPECTED RESULT: checking finishes without errors
  6. 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
    5. modify schema in schema view/properties
    • EXPECTED RESULT: All views should keep in sync
  7. 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
  8. 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
    • Expected Result: same as in Column View
  7. 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
  8. 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
  9. 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
  10. 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: Design View Palette

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

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
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo