TS 61 componetinspector

Revision as of 07:13, 30 March 2012 by MackSix (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

Form Editor - Component Inspector Test Specification

Author: Jana Maleckova, Jaromir Uhrik
Version: 6.1
Last update: 2011/09/14
Introduction: This is intended as tests of component Inspector. (In 7.1 Inspector merged with Navigator)

Contents


Test suite: General

Purpose: Test assure Component Inspector functionality as a component which cooperates with Source Editor , Explorer and Form Editor.
Setup: Start IDE with clear userdir. Create new project, Java Application (e.g. MyApplication) and create a new form (e.g JFrame) containing several components.

  1. Assure the pop-up menu context
    1. Select component (top level component) and assure visual appearance of pop-up menu, enabling/disabling of appropriate/ inappropriate operations according to a pop-up menu context
    • EXPECTED RESULT:
  2. Assure the data transfer actions (clipboard, delete)
    1. Moving/Copying operation are not trivial like in the Explorer. Assure that properties of copied components persists (expect the unique properties e.g. Variable Name - check uniqueness). Refer these changes with Source Editor
    2. Try to rename component. Set new name as name of existing component. Rename component to name of deleted component
    3. Try to select more components and (Cut/Copy) to another container. Cut/Copy container, and try to "nest" it, try it with (J)PopupMenu and (J)Menu
    • EXPECTED RESULT:
  3. Assure consistence with form sub tree of Form Data Object Node
    1. Every opened Form Data Object consists of class sub-node and form sub-node in Explorer (expand the form node in Explorer and expand Top-node in Component Inspector)
    2. Refer all changes in AWT tree of Component Inspector with the form sub-node tree of Explorer. Verify their consistency. These two trees should be the same and operation over one tree should affect the other
    3. Open some form and assure there is new tab added into the editor pane. The name of the tab ends with Form suffix
    • EXPECTED RESULT:
  4. Assure consistence of Component Inspector and Form Window
    1. Traverse through tree
    2. By the selection of node (component or top level component) also its "mirror" component in Form Window is selected
    3. Also Component Inspector's built-in propertysheet should show properties of the selected components
    • EXPECTED RESULT:
  5. Change order
    1. Assure Change order in Component Inspector (in Top-node by Change order and in component by Move up/down )
    2. Check changes in Source Editor (for GridLayout, FlowLayout, CardLayout, BoxLayout, BorderLayout the order change visual appearance in Form Editor, but for another layout must stay without change)
    • EXPECTED RESULT:
  6. Go to actions from the Navigator window
    1. Assure focus traverse (the focus must be moving in the Navigator tree when pressing arrow up and arrow down key in the Editor)
    2. Push Goto Source actions from popup menu in the Navigator
    • EXPECTED RESULT: The source editor for the form is focused, caret is placed appropriately.


Test suite: Testing various Previews

Purpose: To test if previews in various L&F are working
Setup: Start IDE with clear userdir. Create new project, Java Application (e.g. MyApplication) and create a new form (e.g JFrame) containing several components like, jCombobox, jLabel, jTable, jTree, jList, various controls and containers

  1. Test Metal L&F
    1. Open design form in design
    2. Select
      [Frame]
      node in navigator
    3. Invoke popup menu and choose Preview Design -> Metal
    • EXPECTED RESULT: Preview is opened with the same component's layout as is seen in design. No exception is thrown
  2. Test Nimbus L&F
    1. Open design form in design
    2. Select
      [Frame]
      node in navigator
    3. Invoke popup menu and choose Preview Design -> Nimbus
    • EXPECTED RESULT: Preview is opened with the same component's layout as is seen in design. No exception is thrown
  3. Test CDE/Motif L&F
    1. Open design form in design
    2. Select
      [Frame]
      node in navigator
    3. Invoke popup menu and choose Preview Design -> CDE/Motif
    • EXPECTED RESULT: Preview is opened with the same component's layout as is seen in design. No exception is thrown
  4. Test Windows L&F
    1. Open design form in design
    2. Select
      [Frame]
      node in navigator
    3. Invoke popup menu and choose Preview Design -> Windows
    • EXPECTED RESULT: Preview is opened with the same component's layout as is seen in design. No exception is thrown
  5. Test Windows Classic L&F
    1. Open design form in design
    2. Select
      [Frame]
      node in navigator
    3. Invoke popup menu and choose Preview Design -> Windows Classic
    • EXPECTED RESULT: Preview is opened with the same component's layout as is seen in design. No exception is thrown
  6. Test Custom L&F

(see http://netbeans.org/bugzilla/show_bug.cgi?id=204569) - do not use JSlider in tested form.

    1. Open Palette Manager from popup menu invoked on Palette
    2. Press button Add from Jar ...
    3. Choose e.g. Media:JTattoo.jar from your disk
    4. Select listed JTattoo component and press next
    5. Choose Look and Feel Category
    6. Press Finish
    7. Press Close
    8. Select
      [Frame]
      node in navigator
    9. Invoke popup menu and choose Preview Design -> choose some new added L&F.
    • EXPECTED RESULT: Preview is opened with the same component's layout as is seen in design. No exception is thrown
  1. Test Button Group in Preview
    1. Open design form in design
    2. Add e.g. 2 jRadioButtons and assign them to one jButtonGroup
    3. Select
      [Frame]
      node in navigator
    4. Invoke popup menu and choose one of the Preview Design
    • EXPECTED RESULT: Check if only one jRadioButton could be selected in preview
  2. Test all prevous usecases on different platforms
    • EXPECTED RESULT: Should work


Test suite: Layouts category

Purpose: Layouts category in this test assure operation with layouts and their transformation.
Setup: Start IDE with clear userdir. Create new project, Java Application (e.g. MyApplication) and create a new form (e.g JFrame) containing several components.

  1. Assure property of all
    1. Change a property and observe code and visual changes
    • EXPECTED RESULT:
  2. Assure layouts constraints
    1. Change a property and observe code and visual changes.
    • EXPECTED RESULT:
  3. Assure changes by Visual Development
    1. Change location of component by mouse in Form Editor and assure change value of properties in Layout category
    2. Change properties in GridBag Customizer and assure change value of properties in Layout category
    • EXPECTED RESULT:


Test suite: Beans tests

Purpose:
Setup: Start IDE with clear userdir. Create new project, Java Application (e.g. MyApplication) and create a new form (e.g JFrame) containg several components.

  1. Beans test
    1. Create beans by compilation of components (JPanel) add to Component Palette
    2. Try to add to frame (JForm), compile, save, reopen and assure created frame
    • EXPECTED RESULT:
  2. Customizer and AWT
    1. Open form file with AWT components ( top-component)
    2. Move Form Editor window over all desktop pane
    3. Open more than one AWT frame and assure repainting crossovers forms
    • EXPECTED RESULT:


Attachments

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