TS VW 65 WoodstockBasicComponents

Woodstock Basic Components Test Specification for "NetBeans 6.5"

Author: Jaroslav Pospisil
Version: 1.0
Estimated time: 2 hours
Default IZ component(s): visualweb / components
Last update: 24/04/2008
Introduction: This test specification covers the Woodstock Basic Components in the IDE.
Comments: __This specification covers current state of Woodstock Basic Components (24/04/2008).

Contents




\

Test specification setup
\

In order to complete this test specification, some preparatory work is needed to do first. We test in Netbeans 6.1, full version of installer, and default Glassfish v2ur1 server, installed along with IDE. All basic Woodstock components are tested in environment of JavaEE5 Web application with Visual Web JSF framework included.

  • Download and install IDE - you can left everything default, just keep pressing Next and Finish.
  • Start IDE and from Main menu select File > New Project > Web > Web Application
  • Click Next three times and then check Visual Web JavaServer Faces checkbox.
  • Click Finish.

New Web project will open with Page1.jsp selected in editor and to the right of IDE screen is now visible Palette window

Common test cases

Basic Woodstock components could be divided into groups and subgroups, according to its functionality. There's however couple of test cases, comon to all or many basic Woodstock components. In this test specification, we test this common test cases.
\

  • Test case: Drag and Drop component from palette
  • Test case: Resize component
  • Test case: Data Bind
  • Test case: Client Side Behaviour


\



\

Test suites


\

Test suite: Drag and Drop component from palette

Setup:

  • None.


\

  1. Drag and Drop LABEL component
    1. Drag and drop Label component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • {{result|EXPECTED RESULT: Label is added and cursor is blinking behind black Label word to enter label text. On the right side of screen is Label1:Label - Properties window opened and component is added also in tree structure in Navigator.
  2. Drag and Drop STATIC TEXT component
    1. Drag and drop Static text component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Static text is added and cursor is blinking behind light gray Static text word to enter text. On the right side of screen is Static text1 - Properties window opened and component is added also in tree structure in Navigator.
  3. Drag and Drop ANCHOR component
    1. Drag and drop Anchor component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Anchor - with anchor icon - is added. On the right side of screen is Anchor1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop MESSAGE component
    1. Drag and drop Message component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Message text field is added. On the right side of screen is message1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop MESSAGE GROUP component
    1. Drag and drop Message Group component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Message Group text field is added. On the right side of screen is messageGroup1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop TEXT FIELD component
    1. Drag and drop Text Field component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Text field is added. On the right side of screen is textField1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop TEXT AREA component
    1. Drag and drop Text Area component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Text area is added. On the right side of screen is textArea1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop PASSWORD FIELD component
    1. Drag and drop Password Field component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Password field is added. On the right side of screen is passwordField1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop HIDDEN FIELD component
    1. Drag and drop Hidden Field component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Hidden field is added, although not visible. On the right side of screen is hiddenField1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop CALENDAR component
    1. Drag and drop Calendar component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Calendar is added. On the right side of screen is calendar1 - Properties window opened and component is added also in tree structure in Navigator.
 
  1. Drag and Drop FILE UPLOAD component
    1. Drag and drop File Upload component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: File Upload is added. On the right side of screen is fileUpload1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop LISTBOX component
    1. Drag and drop Listbox component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Listbox is added. On the right side of screen is listbox1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop CHECKBOX component
    1. Drag and drop Checkbox component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Checkbox is added. On the right side of screen is checkbox1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop CHECKBOXGROUP component
    1. Drag and drop Checkbox Group component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Checkbox Group is added. On the right side of screen is checkboxGroup1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop RADIOBUTTON component
    1. Drag and drop Radio Button component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Radio Button is added. On the right side of screen is radioButton1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop RADIOBUTTONGROUP component
    1. Drag and drop Radio Button Group component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Radio Button Group is added. On the right side of screen is radioButtonGroup1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop DROPDOWNLIST component
    1. Drag and drop Drop Down List component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Drop Down List is added. On the right side of screen is dropDown1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop BUTTON component
    1. Drag and drop Button component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Button is added. On the right side of screen is button1:Button - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop HYPERLINK component
    1. Drag and drop Hyperlink component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Hyperlink is added. On the right side of screen is hyperlink1:Hyperlink - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop IMAGE HYPERLINK component
    1. Drag and drop Image Hyperlink component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Image Hyperlink is added. On the right side of screen is imageHyperlink1:ImageHyperlink - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop IMAGE component
    1. Drag and drop Image component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Image is added. On the right side of screen is image1 - Properties window opened and component is added also in tree structure in Navigator.
  
  1. Drag and Drop TREE component
    1. Drag and drop Tree component from Woodstock Basic tab of Palette to Page1.jsp opened in editor.
    • EXPECTED RESULT: Tree is added. On the right side of screen is tree1:Tree - Properties window opened and component is added also in tree structure in Navigator.
  



Test suite: Resize component

Setup:

  • Complete previous test suite.


\

  1. Drag and Drop LABEL component
    1. Click on Label component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: label1 can be resized both ways and it overlays another component in design view, if resized over it. Text inside stays aligned to top left corner, remains same size and is rearanged, if control boundaries are downsized to affect it.
  2. Resize STATIC TEXT component
    1. Click on staticText1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: staticText1 can be resized both ways and its rectangle don't overlays another component in design view, other than Label, if resized over it. Static text on other hand overlays everything. Text inside stays aligned to top left corner, remains same size and is rearanged, if control boundaries are downsized to affect it.
  
  1. Resize ANCHOR component
    1. Click on anchor1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: anchor1 can be resized both ways and its rectangle don't overlays another component in design view, if resized over it. Anchor on other hand overlays everything. Icon inside stays aligned to top left corner and remains same size.
  
  1. Resize MESSAGE component
    1. Click on message1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: message1 can be resized both ways and its rectangle don't overlays another component in design view, if resized over it. Message text on other hand overlays everything. Text inside stays aligned to top left corner, remains same size and is rearanged, if control boundaries are downsized to affect it.
  
  1. Resize MESSAGE GROUP component
    1. Click on messageGroup1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: messageGroup1 can be resized both ways and its rectangle don't overlays another component in design view, if resized over it. Group red rectangle on other hand overlays everything. Text inside stays aligned to top left corner, remains same size and is rearanged, if control boundaries are downsized to affect it.
  
  1. Resize TEXT FIELD component
    1. Click on textField1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: textField1 can't be resized manually.Text inside is cut, if it overlaps displayed control text area.
  
  1. Resize TEXT AREA component
    1. Click on textArea1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: textArea1 couldn't be resized manually.Text inside is cut, if it overlaps displayed control text area.
  
  1. Resize PASSWORD FIELD component
    1. Click on passwordField1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: passwordField1 can't be resized manually.Text inside is cut, if it overlaps displayed control text area.
  
  1. Resize CALENDAR component
    1. Click on calendar1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: calendar1 can't be resized manually.
  
  1. Resize FILE UPLOAD component
    1. Click on fileUpload1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: fileUpload1 can't be resized manually.
  
  1. Resize LISTBOX component
    1. Click on listbox1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: listbox1 can't be resized manually.
  
  1. Resize CHECKBOX component
    1. Click on checkbox1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: checkbox1 can be resized both ways and it overlays another component in design view, if resized over it. Text inside stays aligned to top left corner, remains same size and is rearanged,, if control boundaries are downsized to affect it.
  
  1. Resize CHECKBOXGROUP component
    1. Click on checkboxGroup1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: checkboxGroup1 can be resized both ways and its rectangle don't overlays another component in design view, if resized over it. Message text on other hand overlays everything. Text inside stays aligned to the left side, remains same size and is rearanged with control boundaries resizing.
  
  1. Resize RADIOBUTTON component
    1. Click on radioButton1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: radioButton1 can be resized both ways and it overlays another component in design view, if resized over it. Text inside stays aligned to top left corner, remains same size and is rearanged,, if control boundaries are downsized to affect it.
  
  1. Resize RADIOBUTTONGROUP component
    1. Click on radioButtonGroup1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: radioButtonGroup1 can be resized both ways and its rectangle don't overlays another component in design view, if resized over it. Message text on other hand overlays everything. Text inside stays aligned to the left side, remains same size and is rearanged with control boundaries resizing.
  
  1. Resize DROPDOWNLIST component
    1. Click on dropDown1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: dropDown1 can't be resized manually.
  
  1. Resize BUTTON component
    1. Click on button1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: buttonl1 can be resized both ways and it overlays label, static text,textfield,message, message group,dropdownlist and file chooser components in design view. In other cases components overlays button instead. Text inside stays aligned to the center of button, remains same size and is rearanged, if control boundaries are downsized to affect it.
  
  1. Resize HYPERLINK component
    1. Click on hyperlink1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: hyperlink1 can be resized manually.
  
  1. Resize IMAGE HYPERLINK component
    1. Click on imageHyperlink1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: imageHyperlink1 can't be resized manually.
  
  1. Resize IMAGE component
    1. Click on image1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: image1 can't be resized manually.
  
  1. Resize TREE component
    1. Click on tree1 component in editor and after it became selected, try to resize boundaries of its rectangle both directions (make it smaller and bigger than original size). Pull boundaries of control to cross another component boundaries partially and whole.
    • EXPECTED RESULT: tree11 can be resized both ways and it overlays another component in design view, if resized over it. Text inside stays aligned to top left corner, remains same size and is rearanged, if control boundaries are downsized to affect it.
  




Test suite: Data Bind

Setup:

  • Complete previous test suites.
  • Go to Runtime tab and open Databases node.
  • Right-click on jdbc:derby://localhost:1527/sample
    [AppOnAPP]
    node and select Connect.
  • Database will be conected (disconnected icon is replaced with connected) and then open Tables


\

  1. Data Bind LABEL component text
    1. Right-click on label1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. There's no binding yet. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Drag and drop CUSTOMER table on label1 component.
    • EXPECTED RESULT: Label text should change to 123 and if you invoke Bind to Data again, you can see, that component text is now binded to table and new customerDataProvider is added in DataProviders list. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  2. Data Bind STATIC TEXT component text
    1. Right-click on staticText1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Drag and drop PRODUCT table on staticText1 component. Click OK in the window opened.
    • EXPECTED RESULT: Static text text should change to 123 and if you invoke Bind to Data again, you can see, that component is now binded to table and new productDataProvider is added in DataProviders list. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind TEXT FIELD component text
    1. Right-click on textField1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Drag and drop MANUFACTURER table on textField1 component. Click OK in the window opened.
    • EXPECTED RESULT: Text field text should change to 123 and if you invoke Bind to Data again, you can see, that component is now binded to table and new manufacturerDataProvider is added in DataProviders list. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind TEXT AREA component text
    1. Right-click on textArea1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Drag and drop DISCOUNT_CODE table on textArea1 component. Click OK in the window opened.
    • EXPECTED RESULT: Text area text should change to abc and if you invoke Bind to Data again, you can see, that component is now binded to table and new discount_codeDataProvider is added in DataProviders list. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind PASSWORD FIELD component
    1. Right-click on passwordField1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Drag and drop PRODUCT_CODE table on textArea1 component. Click OK in the window opened.
    • EXPECTED RESULT: Component don't change visually, but if you invoke Bind to Data again, you can see, that component is now binded to table and new product_codeDataProvider is added in DataProviders list. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind HIDDEN FIELD component
    1. Right-click on hiddenField1 in Navigator to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Drag and drop MICRO_MARKET table on textArea1 component. Click OK in the window opened.
    • EXPECTED RESULT: If you invoke Bind to Data again, you can see, that component is now binded to table and new micro_marketDataProvider is added in DataProviders list. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind CALENDAR component
    1. Right-click on calendar1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select product_codeDataProvider and select PRODUCT_CODE.PROD_CODE String data field.
    • EXPECTED RESULT: In the textfield you will see abc string. Property Bindings... window contains all available properties and also list of bindable values for Page1.
 
  1. Data Bind FILE UPLOAD component
    1. Right-click on fileUpload1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select micro_marketDataProvider and select MICRO_MARKET.ZIP_CODE String data field.
    • EXPECTED RESULT: Textfield will not change. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind LISTBOX component
    1. Right-click on listBox1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select customerDataProvider and select CUSTOMER.NAME,CUSTOMER.NAME String Value and Display field.
    • EXPECTED RESULT: In the listbox you will see three abc strings. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind CHECKBOX component
    1. Right-click on checkBox1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select customerDataProvider and select CUSTOMER.CUSTOMER_ID Integer Data field.
    • EXPECTED RESULT: Checkbox will not change. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind CHECKBOXGROUP component
    1. Right-click on checkBoxGroup1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select productDataProvider and select PRODUCT.DESCRIPTION,PRODUCT.DESCRIPTION String Value and Display field.
    • EXPECTED RESULT: In the labels area you will see three abc strings. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind RADIOBUTTON component
    1. Right-click on radioButton1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select micro_marketDataProvider and select MICRO_MARKET.RADIUS Double Data field.
    • EXPECTED RESULT: Radiobutton will not change. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind RADIOBUTTONGROUP component
    1. Right-click on radioButtonGroup1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select discount_codeDataProvider and select DISCOUNT_CODE.DISCOUNT_CODE,DISCOUNT_CODE.DISCOUNT_CODE String Value and Display field.
    • EXPECTED RESULT: In the labels area you will see three abc strings. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind DROPDOWNLIST component
    1. Right-click on dropDown1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select productDataProvider and select PRODUCT.PRODUCT_CODE,PRODUCT.PRODUCT_CODE String Value and Display field.
    • EXPECTED RESULT: In the labels area you will see a... string. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind BUTTON component
    1. Right-click on button1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select customerDataProvider and select CUSTOMER.CITY String Data field.
    • EXPECTED RESULT: Button text will change to abc. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind HYPERLINK component
    1. Right-click on hyperlink1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select customerDataProvider and select CUSTOMER.PHONE String Data field.
    • EXPECTED RESULT: Hyperlink text will change to abc. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind IMAGE HYPERLINK component
    1. Right-click on imageHyperlink1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select customerDataProvider and select CUSTOMER.PHONE String Data field.
    • EXPECTED RESULT: Image hyperlink text will change to abc. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind TREE component
    1. Right-click on tree1 to invoke context menu and select Bind to Data
    2. Check that both Bind to Data Provider and Bind to Object options are available. Close the dialog.
    3. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    4. Open Bind to Data again, select manufacturerDataProvider and select MANUFACTURER.NAME String Data field.
    • EXPECTED RESULT: Tree root text will change to abc. Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind ANCHOR component
    1. Anchor doesn't have Data Bind action enabled in context menu, so we can bind only Properties. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    • EXPECTED RESULT: Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind MESSAGE component
    1. Message doesn't have Data Bind action enabled in context menu, so we can bind only Properties. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    • EXPECTED RESULT: Property Bindings... window contains all available properties and also list of bindable values for Page1.
  
  1. Data Bind MESSAGE GROUP component
    1. Message Group doesn't have Data Bind action enabled in context menu, so we can bind only Properties. Open context menu and select Property Bindings... to check available list of properties and possible bindings.
    • EXPECTED RESULT: Property Bindings... window contains all available properties and also list of bindable values for Page1.
  



Test suite: Client Side Behaviour

  1. Add Binding Attribute action

Valid for all Woodstock basic components.
\

    1. Right-click on the component to invoke context menu.
    2. Select Add Binding Attribute action.
    • {{{1}}}
  1. Remove Binding Attribute action
    1. Opposite of previous action - removes all code added.
    • {{{1}}}
  2. Auto-Submit on Change action

Available for all components except __Label, Static Text, Message, Message Group, Hyperlink, Image Hyperlink, Image and Button.
\

    1. Right-click on the component to invoke context menu.
    2. Select Auto-Submit on Change action.
    • EXPECTED RESULT: In JSP view is added parameter onClick for the component.

onClick="webui.suntheme4_2.common.timeoutSubmitForm(this.form, 'checkbox1');"


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