TS 61 MobilityFlowDesigner

Flow Designer Test Specification

Author: Petr Dvorak (rewritten from the text by Fabiola Gallegos Rios)
Last update: 03/03/2008
Introduction: This set of test cases verifies the behavior of the Flow designer.

Contents


Test suite: Palette Pop-up Menu

Purpose: Verify the behavior of the pop-up menu elements.
Setup: Right-click in the Palette window

  1. Create new Category
    1. Select Create New Category from the pop-up menu
    2. Fill in the field New Category Name and click OK
    • EXPECTED RESULT: The new category must be added in the Palette window.
  2. Hide & Show Item Names
    1. Select Hide Item Names (or Show Item Names, respectively) from the pop-up menu.
    • EXPECTED RESULT: The item names are properly hidden or shown
  3. Show Big & Small Icons
    1. Select Show Big Icons (or Show Small Icons, respectively) from the pop-up menu.
    • EXPECTED RESULT: The size of the icons displayed in the Palette window must be modified
  4. Change the Order of the Categories
    1. Select a Palette manager from the pop-up menu (a window Palette Manager appears).
    2. Select one category from the list
    3. Click Move up or Move down buttons to move categories
    • EXPECTED RESULT: The new category order is shown in the Palette manager and in the Palette window. If the first (the last) category is selected, Move up (Move down) button is disabled.
  5. Palette Manager - create a new category
    1. Setup: If you closed a Palette manager window after the previous test case, reopen it: select a Palette manager from the pop-up menu (a window Palette Manager appears).
    2. Click New Category. Window with a title New Palette Category will show up.
    3. Fill in a category name and click OK.
    • EXPECTED RESULT: New category is created in the Palette Manager and in the Palette window
  6. Palette Manager - adding a component to the Palette
    1. Setup: If you closed a Palette manager window after the previous test case, reopen it: select a Palette manager from the pop-up menu (a window Palette Manager appears).
    2. Click Add To Palette button. A wizard for adding a new component to the palette shows up.
    3. On the first page, select the project from which you would like to add the component.
    4. Click Next and proceed to the second step of wizard.
    5. The Show Components From Libraries checkbox must be unchecked by default. Check it - the classes will appear in the list.
    6. Try to select a class to add.
    7. Try to use Select All button.
    8. Try to use Deselect All button.
    9. Select some class(es) in the list and click Finish.
    • {{{1}}}
  7. Palette Manager - removing a component from the Palette
    1. Setup: If you closed a Palette manager window after the previous test case, reopen it: select a Palette manager from the pop-up menu (a window Palette Manager appears).
    2. Select some previously added component (otherwise the Remove button is disabled) and click Remove. Confirm your decision in the Confirm Palette Content Removal window.
    3. Select some user-created category (otherwise the Remove button is disabled) and click Remove. Click Yes to confirm your choice.
    • EXPECTED RESULT: Category or the component is removed from the Palette Manager and also from the Palette window


Test suite: Drag&drop components from the Palette

Purpose: Specifies a behavior of the items when you drag&drop them into the Flow designer.
Setup: Open Visual Design document, open a Flow designer.

  1. Screens
    1. Drag and drop some of the screens (pick randomly at least five screens from those: TextBox, List, Form, Alert, SplashScreen, WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer) from the Displayables group in the Palette window to the Flow designer.
    • EXPECTED RESULT: The screens have to appear in the Flow designer. The Navigator window has to display all the screens that have been added to the Visual Design. Selection in the Flow designer has to be synchronized with the selection in the Navigator window and with the content of the Properties window.
  2. Commands
    1. Drag&drop each command from the Commands group in the Palette to the TextBox, List, Alert, Form, SplashScreen, WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer and also to the background in the Flow designer.
    • EXPECTED RESULT: Commands have to appear inside the screens in the Flow designer. The Navigator window has to display all commands that have been added to the Visual Design. The action must be disabled for the background of the Flow designer.
  3. Form Items
    1. Drag&drop each item from the Items category to the Form screen in the Flow designer.
    2. Drag&drop each item from the Items category to the TextBox, List, Alert, SplashScreen, WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer screens and also to the background in the Flow designer.
    • EXPECTED RESULT:
      Action 1: The Form Items have to appear in the Navigator window. The Navigator window has to display 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 screen and for the background of the Flow designer.
  4. List Element
    1. Drag&drop a List Element from the Elements category in the Palette to the List Screen in the Flow designer.
    2. Drag&drop a List Element from the Elements category in the Palette to the Form, TextBox, Alert, SplashScreen, WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer screens and also to the background in the Flow designer.
    • EXPECTED RESULT:
      Action 1: The List Element(s) have to appear inside the List screen in the Flow Design. The Navigator window displays List Element(s) that have been added to the List Screen.
      Action 2: The action must be denied for each Alert, List, TexBox, SplashScreen, WaitScreen, SplashScreen, WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer screen and for the background of the Flow designer
  5. Resources
    1. Drag&drop a Ticker resource from the Palette (category Resources) to the screens (Form, TextBox, List, Alert, SplashScreen, WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer) in the Flow designer.
    2. Drag&drop Image and Font resources from the Palette (category Resources) to the screens (Form, TextBox, List, Alert, SplashScreen, WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer) in the Flow designer.
    • EXPECTED RESULT:
      Action 1: Ticker resource have to appear in the Navigator window. The Navigator Window displays all the resources that have been added in the Visual Design in a tree formation.
      Action 2: Font and Image resource can be assigned to the WaitScreen and the SplashScreen (as these can contain an image and a string). Font and Image resource cannot be assigned to another types of screen.
  6. Flow
    1. Drag&drop an Entry Point, Call Point, IF and Switch from the Flow category to the Flow designer.
    • EXPECTED RESULT: The screens have to appear in the Flow designer. The Navigator window must display all flow control components that have been added to the Visual Design in a tree formation. Selection in the Flow designer has to be synchronized with the selection in the Navigator window and with the content of the Properties window.
  7. Custom Components
    1. Make sure that some custom components are added in the Palette. (To learn about how to add a custom component, see ManagerTestSpecifictions document.)
    2. Drag&drop some custom components from the component palette to the Flow designer.
    • EXPECTED RESULT: Some of these components can be added in the Flow designer - it depends on the type of a custom component.
  8. Choice Element
    1. Drag&drop a Choice Element from the component palette to every type of screen (Form, TextBox, List, Alert, SplashScreen,WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer) and also to the background of the Flow designer.
    • EXPECTED RESULT: The action must be denied for every screen and for the background of the Flow designer


Test suite: Palette Category Flow

Purpose: Specifies a behavior of the components from the Flow category when you drag&drop them into the Flow designer.
Setup: Open Visual Design document and open a Flow designer.

  1. Entry Point
    1. Drag&drop an Entry Point component from the Palette (Flow category) to the Flow designer of the Visual MIDlet that you want to extent.
    • EXPECTED RESULT: An Entry Point acts like a source point for transitions in the Flow. It represents a method in the source file. The code must be generated into the method body (check it).
  2. Call Point
    1. Drag&drop a Call Point component from the Palette (Flow category) to the Flow designer.
    • EXPECTED RESULT: The Call Point acts like a target point for transitions in the Flow. The generated code must contain a call to the specified method (check it).
  3. List Action
    1. Drag&drop all commands (components under the Command category in the Palette) to the List screen.
    2. Drag&drop a List Action from the component palette to the commands assigned to the List screen in Flow designer.
    3. Drag&drop a List Action from the component palette to a Form, TextBox, Alert, SplashScreen, WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer screens and also to the background of the Flow designer.
    • EXPECTED RESULT:
      Action 1: New methods are added to the source code (check it).
      Action 2: The List Action icon have to appear next to the command assigned to the List screen in the Flow designer. The Navigator window 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 that belongs to Alert, List, TexBox, SplashScreen, WaitScreen, SplashScreen, WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer screens and also for the background of the Flow designer.
  4. Previous Screen
    1. Open or create a mobile project with Visual MIDlet file with more screens connected with each other in the Flow designer.
    2. Drag&drop Previous Screen component from the Flow category in the Palette to some of the action that is assigned to a screen in the Flow designer.
    • EXPECTED RESULT: The icon must appear by the command. If a command was previously pointing to some other node, the arrow is removed. Previous Screen component should allow user to go to the previous screen of the application. Check the functionality of a Previous Screen component in the emulator.
  5. IF
    1. Drag&drop an IF component from the Flow category in the Palette to the Flow designer.
    • EXPECTED RESULT: The IF statement encloses a code which is executed only if some specified condition holds (connect the IF component to some other objects in the Flow designer, fill in the condition in the Properties window and check the generated code).
  6. Switch
    1. Drag&drop a Switch component from the Flow category in the Palette to the Flow designer.
    2. Drag&drop several Switch Case components from the component palette to the Switch component in the Flow designer.
    • EXPECTED RESULT: Check the source code - the "switch code" must be generated properly and there must be a "case" for each Switch Case inserted to the Switch component.
  7. Switch Case
    1. Drag&drop a Switch Case from the component palette to the Switch Screen in the Flow designer.
    2. Drag&drop a Switch Case from the component palette to some of the other screens (choose randomly from Form, TextBox, Alert, SplashScreen, WaitScreen, PIMBrowser, FileBrowser, Login Screen, SMScomposer) and also to the background of the Flow designer.
    • EXPECTED RESULT:
      Action 1: The Switch Case have to appear in the Switch component in the Flow designer. The Navigator window displays all the Switch Cases that have been added to the Switch Screen in a tree formation.
      Action 2: The action must be denied for all the screens and also for the background of the Flow designer.


Test suite: Flow Designer - Screens, Transitions and Ports

Purpose: Verify the behavior of the elements, ports and transitions in the Flow designer.
Setup: Open a Mobile Application with the elements in the Flow designer.

  1. Dragging Screen or Transition
    1. Drag a screen in the Flow designer.
    2. Drag a transition (the arrow) leading from some screen port to some another screen port.
    • EXPECTED RESULT:
      Action 1: A screen starts to move - all transitions (leading "to" or "from" the screen) remains connected and are re-routed nicely. If a mouse cursor is moving out of the visible part of the scene, the view should start scrolling in appropriate direction.
      Action 2: Transitions are correctly modified.
  2. Select a screen or transition
    1. Click on a screen or transition in order to select it.
    • EXPECTED RESULT: Clicked screen (transition) is selected. All the transitions that are leading "to" or "from" a selected node (screen) are highlighted (with different color than the selected node). Selection in the Flow designer has to be synchronized with the selection in the Navigator Window and with the content of the Properties window.
  3. CTRL key
    1. Hold CTRL key during selection.
    • EXPECTED RESULT: It must be possible to select more items by clicking on them while simultaneously holding a CTRL key.
  4. Right mouse button
    1. Right-click a node, a link, or the background.
    • EXPECTED RESULT: An appropriate pop-up menu should be shown.


Test suite: Flow designer toolbar

Purpose: Specifies the behavior of the Flow designer toolbar buttons.
Setup: Open a Mobile Application with some elements in the Flow designer.

  1. Layout
    1. Click a Layout button in the Flow designer toolbar
    • EXPECTED RESULT: All objects in the Flow designer are reorganized so that they fit better in the scene. Transitions remains preserved.
  2. Overview
    1. Click the Overview button in the Flow designer toolbar
    • EXPECTED RESULT: A small overview of the scene should be displayed right bellow the Overview button. If the scene is too big to fit to the Flow designer, it must be possible to use the miniature overview to navigate in the scene.
  3. Collapse/Expand all buttons
    1. Click Collapse All button in the Flow designer toolbar
    2. Click Expand All button in the Flow designer toolbar
    • EXPECTED RESULT: All nodes (screens) in the Flow designer must collapse/expand (which means they have to hide/show assigned commands, list items, switch cases, ...).
  4. Export Flow as Image
    1. Right-click in the Flow designer and choose "Export Flow as Image" from the pop-up menu.
    2. Specify the file name and the location of the file.
    • EXPECTED RESULT: An IDE creates an image (PNG) capturing the content of the Flow designer.


Test suite: Other

Purpose: Other actions
Setup: Open a Mobile Application with a Visual Design

  1. Open Visual Design
    1. Right-click the visual MIDlet in the Project window and invoke the Open action from the pop-up menu.
    • EXPECTED RESULT: The visual MIDlet you right-clicked opens in the Flow designer.
  2. Edit Visual Design
    1. Right-click the visual MIDlet in the Project window and invoke the Edit action from the pop-up menu.
    • EXPECTED RESULT: The visual MIDlet you right-clicked opens in the Source view.
  3. Add (by means of the action in the Navigator window)
    1. Invoke Add action from the pop-up menu in the Navigator window.
    2. Select a component to be added.
    • EXPECTED RESULT: The component is added to the Navigator and to the Flow designer.
  4. Delete (by means of the action in the Navigator window)
    1. Right-click the component in the Navigator and invoke a Delete action from the pop-up menu.
    2. Confirm your decision to delete a component in the dialog.
    • EXPECTED RESULT: The component is deleted. Relevant source code is removed. The component is removed from Flow designer.
  5. Order of the commands in the Navigator window
    1. Invoke Move Up/Move Down action from the pop-up menu on some previously added command that is under Assigned Commands in the Navigator.
    • EXPECTED RESULT: The command is moved up/down.
  6. Rename (by means of the action in the Navigator window)
    1. Right-click some component in the Navigator and invoke a Rename action from the pop-up menu.
    2. Fill in a new name of the component in the dialog.
    • EXPECTED RESULT: The selected component is renamed to the name you have specified (and you see the change in the Flow designer and in the Properties window).




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