TS 60 MobilityFlowDesigner

Flow Design Test Specification

Author: Fabiola Gallegos Rios
Version: 3.0.0
Lastupdate: 1.2.2008
Introduction: Verify the behavior of Popup Menu options

Contents


Test suite: Palette Popup Menu

Purpose: Verify the behavior of Popup Menu elements.
Setup: Right Click in the Component Palette

  1. Create new Category
    1. Will appear New Palette Category window.
    2. Fill New Category Name and Click OK
    • EXPECTED RESULT: The new Category will be added in the Component Palette.
  2. Hide & Show Item Names
    1. Press Hidden Item Names or Show Item Names button.
    • EXPECTED RESULT: The Item Names will be Hidden or Show
  3. Show Big & Small Icons
    1. Press Show Big or Small button.
    • EXPECTED RESULT: The size of the Icons will be modified
  4. Change Categories Order
    1. Will apear Change Order Window, the first Category must be selected and move button must be unavailable.
    2. Select one Category
    3. Click Move up or Move down button
    • EXPECTED RESULT: The new Category Order will be showed in tne Component Palette.
  5. Palette Customizer
    1. Add From Project button. A wizard for adding new component to the palette appears. On the first page, select the project from which you would like to add the component. Click Next, the Show_Components _From_Libraries box must be unchecked. Check and will appear the class. Try to Select a class to add. Try Select Alll Button. Try Unselect Alll Button , In this dialog you can also specify the palette category to which the component is going to be added.Click Finish on the wizard.
    2. Move Up Button. Select one Category.Change Categories Order.
    3. Move Down Button. Select one Category. Change Categories Order.
    4. Remove. Select one Category. Confirm Palette Content Removal Window must appear. Click Yes or Not.
    5. New Category.Will appear New Palette Category window.Fill New Category Name and click OK
    • EXPECTED RESULT: Add From Project button. The new component should be now visible under the specify palette category node. The new component is now available for the visual design. Move Up Button & Move Down Buttons. The new categories order will be appear in the Component Palette. Remove. If you press YES, the category must disappear in the Component Palette. New Category. The new Category will be added in tne Component Palette.


Test suite: Drag&Drop Components from the Palette

Purpose: Specifies behavior of the items when you Drag&Drop into the Flow Desing.
Setup: Open Visual Desing document and click in Flow Desing.

  1. Screens
    1. Click and drag each screen ( TextBox, List, Form, Alert,SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer) from the Screens group in the component palette to the Flow Design.
    • EXPECTED RESULT: The Screens have to appear in the Flow Design and the Navigator Window will displays all screens that have been added to the visual design in a tree formation. Selection has to be synchronized with the selection in the Navigator Window and Property Sheet window.
  2. Commands
    1. Drag&Drop each Command from the Commands group in the component palette to the Screens (TextBox,List,Alert,Form,SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer) and background in Flow Design.
    • EXPECTED RESULT: The Commands have to appear next to the screens in the Flow Design and the Navigator Window will displays all commands that have been added to the visual design in a tree formation.
  3. Form Items
    1. Drag&Drop each Form Item from the component palette to the Form Screen in Flow Design.
    2. Drag&Drop each Form Item from the component palette to the TextBox,List,Alert,SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer screens and background in Flow Design.
    • EXPECTED RESULT: Action 1: The Form Items have to appear in the Navigator Window. The Navigator Window will displays all Form Items that have been added to the Form Screen in a tree formation. Action 2: The action must be denied for each Alert, List, TexBox,WaitScreen,SplashScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer Screens and Mobile Divice
  4. List Element
    1. Drag&Drop List Element from the component palette to List Screen in Flow Design.
    2. Drag&Drop List Element from the component palette to Form,TextBox,Alert,SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer screens and background in Flow Design.
    • EXPECTED RESULT: Action 1: The List Element have to appear next to the List screen in the Flow Design .The Navigator Window will displays all List Elements that have been added to the List Screen in a tree formation.Action 2: The action must be denied for each Alert,List,TexBox,SplashScreen,WaitScreen,SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen, SMScomposer screens and Mobile Divice in the Flow Design
  5. Resources
    1. Drag&Drop Ticker Resource from the component palette to the Screens (Form,TextBox,List,Alert,Splash,WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer) in Flow Design.
    2. Drag&Drop Image and Font resources from the component palette to the Screens(Form,TextBox,List,Alert,Splash and WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer) in Flow Design.
    • EXPECTED RESULT: Accion 1: Ticker Resource have to appear in the Navigator Window. The Navigator Window will displays all the Resources that have been added in the Visual Design in a tree formation. Accion 2: Image and Font Resources Don't have to appear in the Navigator Window and Screen Design, because these resources only can be added in the FormItems StringItem and ImageItem respectevely.
  6. Flow
    1. Click and drag each the follow screens: Entry Point,Call Point,IF,Switch Case from the Flow category in the component palette to the Flow Design.
    • EXPECTED RESULT: The Screens have to appear in the Flow Design and the Navigator Window will displays all screens that have been added to the visual design in a tree formation. Selection has to be synchronized with the selection in the Navigator Window and Property Sheet window.
  7. Custom Components
    1. Be sure that Custom Components have been added berfore in the Component Palette. To add Custom Componentes SEE MangerTestSpecifictions Document.
    2. Drag&Drop Custom Components from the component palette to Flow Design.
    • EXPECTED RESULT: Some of this components can be added in Flow Designer, it will depend of the custom compnents that the user specifies
  8. Choice Element
    1. Drag&Drop Choice Element from the component palette to each Screen (Form,TextBox,List,Alert, SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer) and background in Flow Design.
    • EXPECTED RESULT: The action must be denied for every Screen and Mobile Divice in the Flow Design


Test suite: Palette Category Flow

Purpose: Specifies behavior of the components when you Drag&Drop into the Flow Desing of this category.
Setup: Open Visual Desing document and click in Flow Desing.

  1. Entry Point
    1. Drag&Drop Entry Point component from Flow Category Palette to the Flow Design of the Visual MIDlet that you want to extent.
    • EXPECTED RESULT: An Entry Point acts like a Source Point for Transitions in Flow. It represents a method in the source file. The code will be generated into the method body.
  2. Call Point
    1. Open a Midlet file where you want to add the Call Point.
    2. Drag&Drop Call Point component from Flow Category Palette to the Flow Design.
    • EXPECTED RESULT: The Call Point acts like a Target Point for Transitions in Flow. The generated code will contain a call to specified method.
  3. List Action
    1. Drag&Drop all Command components from the Palette to the List screen.
    2. Drag&Drop List Action from the component palette to the commands assigned to the List screen in Flow Design.
    3. Drag&Drop List Action from the component palette to Form,TextBox,Alert,SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer screens and background in Flow Design.
    • {{result|EXPECTED RESULT: Action 1: New "list-action" method is added to the source code. Each list component (which is using List Action) has its own method. Action 2: The List Action icon have to appear next to the each command assigned to the List Screen in the Flow Design. The Navigator Window will displays all List Actions that have been added to the List screen in a tree formation. Action 3: The action must be denied for each commands of an Alert,List,TexBox,SplashScreen,WaitScreen,SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer screens and Mobile Device in Flow Design
  4. Previous Screen
    1. Open or create a mobile project with Visual MIDlet file with "screens conected" on Flow Design.
    2. Drag&Drop Previous Screen component from the Palette to Form,TextBox,Alert,SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer screens in Flow Design.
    • EXPECTED RESULT:Will appear in the screen an icon. In the Emulator or real device this command allows an user to walk through screens back and forward..
  5. IF
    1. Drag&Drop IF component from Flow Category Palette to the Flow Design.
    • EXPECTED RESULT:The if statement encloses some code which is executed only if a condition is true
  6. Switch
    1. Drag&Drop Switch component from Flow Category Palette to the Flow Design.
    2. Drag&Drop several Switch Case components from the component palette to Switch Screen in Flow Design.
    • EXPECTED RESULT: When the switch statement executes, it compares the value of the controlling expression to the values of each Switch Case. The program will select the value of the Switch Case that equals the value of the controlling expression and branch down that path to the end of the code block. If none of the Switch Case values match, then none of the codes within the switch statement code block will be executed. Java includes a default label to use in cases where there are no matches. We can have a nested switch within a case block of an outer switch.
  7. Switch Case
    1. Drag&Drop Switch Case from the component palette to Switch Screen in Flow Design.
    2. Drag&Drop Switch Case from the component palette to Form,TextBox,Alert,SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen,SMScomposer screens and background in Flow Design.
    • EXPECTED RESULT: Action 1: The Switch Case have to appear next to the Switch screen in the Flow Design .The Navigator Window will displays all Switch Cases that have been added to the Switch Screen in a tree formation.Action 2: The action must be denied for these Alert,List, TexBox,SplashScreen,WaitScreen,SplashScreen,WaitScreen,PIMBrowser,FileBrowser,Login Screen, SMScomposer screens and Mobile Divice in the Flow Design.


Test suite: Flow Design & Screens,Transitions,Ports

Purpose: Verify the behavior of the elements, ports and links in the Flow Design.
Setup: Open a Mobile Aplication with elemens in the Flow Design.

  1. Dragging Screen or Transition
    1. Dragging a Screen active area.
    2. Dragging a Transition from Screen port to destination Screen port.
    • EXPECTED RESULT: Action 1: It starts to move the node on the screen - all links (that lead in or out) are re-routed. If a mouse is out of the scene, the viewport should start scrolling. Action 2: It starts creating a new transition.NOTE:Some screens have more than one port (e.g. Alert, WaitScreen)
  2. Select a Screen or Transition
    1. Click on a screen or transition and selects it.
    • EXPECTED RESULT: Only Screens and Transitions are selectable. All links that lead in or out the selected node are highlighted (different color from selection color). Selection has to be synchronized with the selection in the Navigator Window and Property Sheet window.
  3. SHIFT key
    1. Press SHIFT key during selection.
    • EXPECTED RESULT: It starts to inverting the selection instead of forcing to select.
  4. Right Mouse's button
    1. Right-click on a node, a link, or the background.
    • EXPECTED RESULT: Action 1: An appropriate popup menu should be shown.


Test suite: Design Toolbar & Flow Design Panel

Purpose: Specifies behavior of the Design ToolBar Buttons.
Setup: Open a Mobile Aplication with elemens in the Flow Design.

  1. Realing Screens Button
    1. Snap to grid
    • EXPECTED RESULT: Action 1:Toggles between displaying and hiding a dotted grid on background of the designer page.
  2. Overview
    1. Snap to grid
    • EXPECTED RESULT: Action 1:Toggles between displaying and hiding a dotted grid on background of the designer page.
  3. Collapse&Expand all buttons
    1. Collapse all button
    2. Expand all button
    • EXPECTED RESULT: Action 1:Toggles between displaying and hiding a dotted grid on background of the designer page.
  4. Convert to MIDP-1.0
    1. Right-click in the Flow Design window and choose Convert to MIDP-1.0.
    • EXPECTED RESULT: Warning Message appear, If you convert from MIDP 2.0 to MIDP 1.0, components and settings that are not compatible with MIDP 1.0 are deleted from the design.
  5. Export Flow Image
    1. Right-click in the Flow Design window and choose Export Flow Image.
    • EXPECTED RESULT:The IDE creates a graphic file in the.Portable Networks Graphics (PNG) format that you can save on your system.


Test suite: Other

Purpose: Other actions
Setup: Open a Mobile Aplication with a visual design

  1. Open visual design
    1. Invoke Open action from popup menu on a visual midlet node in Project view
    • EXPECTED RESULT: The visual midlet opens in Flow view in editor.
  2. Edit visual design
    1. Invoke Edit action from popup menu on a visual midlet node in Project view
    • EXPECTED RESULT: The visual midlet opens in Source view in editor.
  3. Add in Inspector
    1. Invoke Add action from popup menu in Inspector view.
    2. Select a component to be added
    • EXPECTED RESULT: The component is add to Inspector and to the Flow as well
  4. Delete in Inspector
    1. Invoke Delete action from popup menu on a component in Inspector view
    • EXPECTED RESULT: The component is deleted. Source code is removed. The components is removed from Flow/Screen view
  5. Move component in Inspector
    1. Invoke Move action from popup menu on a component in Inspector view
    • EXPECTED RESULT: The component is moved
  6. Rename in Inspector
    1. Invoke Rename action from popup menu on a component in Inspector view
    • EXPECTED RESULT: The component is renamed




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