TS 60 MobilityVisualProperties

MVD Property Sheet Test Specification for

Author: Fabiola Galleros Rios
Version: 3.0.0
Lastupdate: 29.05.2007
Introduction: Verify the behavior of the Property Sheet

Contents

Test suite: Code Properties

Purpose: Verify the behavior of the properties' elements, in the Flow Design or Screen Design.
Setup: Open a Mobile Application with elements in the Flow Design.

  1. Instance Name
    1. The name of the object. Will appear in Instance Name Window, edit the name and press OK.
    • EXPECTED RESULT: The name of the object must change.
  2. Lazy Initialized
    1. The box is checked by default. Uncheck the box.
    • EXPECTED RESULT: If checked, the component is initialized when the MIDlet's startApp() method is invoked. If it is not checked, The component is initialized the first time the component is needed.


Test suite: String Editor

Purpose: Verify components and behavior of String Editor.
Setup: Have some mobile application with elements in flow or screen design. Each screen has some string property editable in string editor.

  1. String Editor
    1. Invoke the String Editor by clicking on the ellipsis (...) button next to some string property.
    2. The values entered in this text box are used as the property value.
    • EXPECTED RESULT: If the User Code for Obtaining String radio button is selected, the property value is used as Java code rather than as a static string.


Test suite: Action Editor

Purpose: Verify components and behavior of Action editor.
Setup: Invoke properties of command assigned to some screen. Click on ellipsis (...) button next to the action property.

  1. Switch to screen
    1. This Option should be checked by default, Select in Target Screen combox one Screen.
    • EXPECTED RESULT: Flow design will be modified with the new target.
  2. Do nothing
    1. Check one of this options.
    • EXPECTED RESULT: The Target Screen will be unavailable, and in the Generated Code box, the IDE shows the code to be generated.


Test suite: Layout Editor

Purpose: Verify components and behavior of Layout Editor.
Setup: Add "Table Item" on form screen, add some "Simple Table Model" resource into the "Table Item". Invoke its properties.

  1. Layout
    • Comments: The LAYOUT_LEFT, LAYOUT_RIGHT, and LAYOUT_CENTER directives indicate horizontal alignment and are mutually exclusive. Similarly, the LAYOUT_TOP, LAYOUT_BOTTOM, and LAYOUT_VCENTER directives indicate vertical alignment and are mutually exclusive.
    1. Invoke the Layout Window by clicking the ellipsis (...) button next to layout property.
    2. The Default Box is checked and the other sections are unavailable.
    3. Uncheck the Default Box.
    4. Make some combinations using different Layout options.
    • EXPECTED RESULT: It has to display the behavior of the selected Layout in the Device Emulator. (See Comments)


Test suite: Constraint Editor

Purpose: Verify components and behavior of Constraint editor.
Setup: Select TextBox or TextField Item.

  1. Restrictive Constraints
    1. NOTE: Behavior of the Restrictive Constraints: Any: The user is allowed to enter any text. Line breaks may be entered. Numeric: The user is allowed to enter only an integer value. Email: The user is allowed to enter an e-mail address.Phone Number: The user is allowed to enter a phone number.URL : The user is allowed to enter a URL.Decimal: The user is allowed to enter numeric values with optional decimal fractions, for example -123, 0.123,or .5.
    2. Invoke the Constraints Window by clicking the ellipsis (...) button next to some constraint property.
    3. ANY is selected by default.
    4. Select one of the Restrictive Constraints (Numeric,Email,Phone Number,URL,Decimal)
    5. Press OK
    • EXPECTED RESULT: It has to display the behavior of the selected constraint in the Device Emulator. (See NOTE)
  2. Constraints
    1. NOTE: Password: Each character of the data might be masked with a * character Uneditable: Indicates that editing is currently disallowed.Sensitive: Indicates that the text entered is sensitive data that the implementation must never store into a dictionary or table for use in predictive Non Predictive:INITIAL_CAPS_WORD: The initial letter of each word should be capitalized INITIAL_CAPS_SENTENCE: The initial letter of each sentence should be capitalized.
    2. Invoke the Constraints Window by clicking the ellipsis (...) button next to some constraint property.
    3. ANY is selected by default.
    4. Select one of the Restrictive Constraints (Password:,Uneditable,Sensitive,Non Predictive,NITIAL_CAPS_WORD,INITIAL_CAPS_SENTENCE)
    • EXPECTED RESULT: It has to display the behaviour of the selected constraint in the Device Emulator. (See NOTE)


Test suite: Common Screen Properties

Purpose: Verify behavior of properties common to all mobility screens.
Setup: Open properties of any screen.

  1. Ticker
    1. Ticker: It has a combo box containing all Tickers that you can added to the Screen. Selecting a Ticker from this drop-down menu.
    • EXPECTED RESULT: It displays the Ticker in the Screen Designer.
  2. Title
    1. Edit the name and preess OK.
    • EXPECTED RESULT: The name of the Title must change in the Screen Designer.


Test suite: SplashScreen

Purpose: Verify components and behavior of SplashScreen properties.
Setup: Have some functioning mobile application with SplashScreen.

  1. Timeout
    1. 5000 is default value.
    2. Enter new TIMEOUT value in Milliseconds.
    • EXPECTED RESULT: The SplashScreen will switch from the specific screen in the TIMEOUT value.
  2. Allow Timeout Interrupt
    1. Allow Timeout Interrupt box is Checked by default
    2. Uncheck Allow Timeout Interrupt box.
    • EXPECTED RESULT: Run the project in default Device Emulator when the SplashScreen appears, press some button to escape; the SplashScreen has to switch at the specific screen.
  3. Text
    1. Invoke the Text Editor by clicking the ellipsis (...) button next to TEXT property. The Text default value may be null .
    2. The values entered in this text box are used as the property value.
    • EXPECTED RESULT: It displays the new text in the Screen Design. If the "User Code for Obtaining String" radio button is selected, the property value is used as Java code rather than as a static string.
  4. Image resource
    1. To assign the Image Resource at Image Property (combo box).
    • EXPECTED RESULT: If this Image Resource has one Image assigned, it will display the image in the Screen Design. If not follow the Image Resource' steps to assign image.
  5. Text Font
    • Comments: See "Font resource"
    1. Assign one Font Resource at Text Font Property (combo box).
    • EXPECTED RESULT: The Font resource values set will appear in Screen Design and in default Device Emulator.


Test suite: WaitScreen

Purpose: Verify components and behavior of WaitScreen properties.
Setup: Have some functioning mobile application with WaitScreen.

  1. Text
    1. Invoke the Text Editor by clicking the ellipsis (...) button next to text property. The Text default value may be null .
    2. The values entered in this text box are used as the property value.
    • EXPECTED RESULT: It displays the new text in the Screen Design. If the "User Code for Obtaining String" radio button is selected, the property value is used as Java code rather than as a static string.
  2. Text Font
    • Comments: See "Font resource"
    1. Assign one Font Resource at Text Font Property (combo box).
    • EXPECTED RESULT: The Font resource values set will appear in Screen Design and in default Device Emulator.
  3. Failure Action
    1. Invoke the Failure Action Window by clicking the ellipsis (...) button next to Action property in "SUCCESS_COMMAND" properties.
    2. "Switch to" option should be checked by default, Select in Target Screen combobox one Screen.
    3. Check "Do nothing" option.
    • EXPECTED RESULT: If one new Target Screen is selected, Flow design will be modified with the new target. If "Do nothing" option is checked This action will not do anything.
  4. Task
    1. Assign the simpleCancellableTask Resource at Task Property (combo box).
    • EXPECTED RESULT: The wait screen will execute the task.
  5. Image
    1. To assign the Image Resource at Image Property (combo box).
    • EXPECTED RESULT: If this Image Resource has one Image assigned, it will display the image in the Screen Design. If not follow the Image Resource' steps of SplashScreen TestSuite to assign image.


Test suite: Alert

Purpose: Verify components and behavior of Alert properties.
Setup: Have some functioning mobile application with Alert.

  1. Timeout
    1. FOREVER is default value. Select ellipsis (...) button, Timeout Window will appear.
    2. Uncheck FOREVER box, and fill TIMEOUT value in Milliseconds.
    • EXPECTED RESULT: The Screen Alert will switch from the specific screen in the TIMEOUT value. If the FOREVER box is checked the Screen Alert doesn't switch.
  2. Alert Type
    1. The combo box containing all alert types. Select a Type from this drop-down menu (ALARM,CONFIRMATION,ERROR,INFO,WARNING).
    • EXPECTED RESULT: Displays the new list Type in the Device Emulator and you can hear different bell for each Alert Type.
  3. User Indicator
    1. User Indicator box is unchecked by default.
    2. Check the box.
    • EXPECTED RESULT: Gauge indicator will appear in the Alert Form in the Screen Design.


Test suite: File Browser

Purpose: Verify components and functionality of File Browser properties.
Setup: Have some mobile application with File Browser.

  1. Filter
    1. Invoke the String Editor by clicking the ellipsis (...) button of the Filter property.
    2. The values entered in this text box are used as the property value.
    • EXPECTED RESULT: If the "User Code for Obtaining String" radio button is selected, the property value is used as Java code rather than as a static string.



Test suite: List

Purpose: Verify components and functionality of list properties.
Setup: Have some functioning mobile application with list.

  1. List Type
    1. The combo box containing all list types. Select a Type from this drop-down menu.
    • EXPECTED RESULT: It displays the new list Type in the Screen Designer. EXCLUSIVE: The radio button specifies the restrictive List Element setting. MULTIPLE : The checkboxes specify other additional List Elements.
  2. Fit Policy
    1. TEXT_WRAP_DEFAULT is the Fit Policy's default value.
    2. The combo box containing the Fit policies. Select a Fit Policy from this drop-down menu.
    3. Fill one List Element with a long String.
    4. Choose TEXT_WRAP_ON.
    • EXPECTED RESULT: It displays the long String of the List Element in two or more lines, in the Screen Design. If you choose TEXT_WRAP_OFF, it displays the long String of the List Element in one line.


Test suite: Login Screen

Purpose: The Login Screen custom component provides a useful user interface with standard elements such as Username Field, Password Field and Login Button. Setup:

  1. Background Color
    1. Select the color.
    • EXPECTED RESULT: It displays the new Background Color on Device Screen.
  2. Foreground Color
    1. Select the color.
    • EXPECTED RESULT: It displays the new Foreground Color on Device Screen.
  3. Use Login Button
    1. Check the box.
    • EXPECTED RESULT: The button will appear on the device screen
  4. Password
    1. Invoke the Password Window by clicking the ellipsis (...) button.
    2. Enter the password.
    • EXPECTED RESULT: It displays the new password on Device Screen.
  5. Username
    1. Invoke the Username Window by clicking the ellipsis (...) button.
    2. Enter the Username
    • EXPECTED RESULT: It displays the new Username on Device Screen.


Test suite: PIM Browser

Purpose:
The PIM Browser is a custom component that provides easy access to standard mobile devices functions like calendar, address book or task list. Setup:

  1. PIM Type
    1. The combo box containing all PIM types. Select a Type from this drop-down menu.
    • EXPECTED RESULT: It displays the new PIM Type on the emulator or real Screen Device


Test suite: SMS Composer

Purpose: The SMS Composer is a custom component that provides a mechanism and user interface to send short message using Short Message Service (SMS). This component utilizes the JSR-120 Wireless Messaging API. This API is not a part of the MIDP 2.0 specification so this custom component can only be deployed to devices that have built-in support for JSR-120. Setup:

  1. Background Color
    1. Select the color.
    • EXPECTED RESULT: It displays the new Background Color on Device Screen.
  2. Foreground Color
    1. Select the color.
    • EXPECTED RESULT: It displays the new Foreground Color on Device Screen.
  3. Automatically Send
    1. Automatically Send box is Checked by default.
    • EXPECTED RESULT: Controls execution of sendSMS method. Default value of sendAutomaticly argument is Boolean.TRUE which means that method sendSMS is invoked when command Send pressed. If sendAutomaticly is Boolean.FALSE then sendSMS method is not invoked after Send command is pressed.
  4. SMS Properties - Message
    1. Invoke the Message Window by clicking the ellipsis (...) button
    2. Enter the Message
    • EXPECTED RESULT: It displays the Message on Device Screen.
  5. Phone Number
    1. Invoke the Phone Number Window by clicking the ellipsis (...) button
    2. Enter the Phone Number
    • EXPECTED RESULT: It displays the Phone Number on Device Screen.


Test suite: TextBox

Purpose:
Setup:

  1. Maximum Size
    1. 120 is default value. Change the value.
    2. Enter Decimal Value.
    • EXPECTED RESULT: Returns the maximum size (number of characters) that can be stored in this TextBox. If you enter a Decimal Value have to appear an Error Screen.
  2. Initial Input Mode
    1. To invoke the Initial Input Mode Editor by clicking the ellipsis (...) button.
    2. The values entered in this text box.
    • EXPECTED RESULT: The initial input mode is a hint to the implementation. If the implementation cannot provide an input mode that satisfies the applications request, it should use a default input mode.


Test suite: Common Command Properties

Purpose: Verify functionality of common command properties.
Setup: Invoke properties on a command assigned to some screen.

  1. Priority
    • Comments: A priority value of one might indicate the most important command, priority values of two, three, four, and so on indicate commands of lesser importance.
    1. One is the value by default for Priority.
    2. Drag&Drop some Commands from the Palette Manager to the Screen Design.
    3. Assing new Priority at the Commands (See Comments)
    4. Run the Project
    • EXPECTED RESULT: The application uses the priority value to describe the importance of this command relative to other commands on the same screen. It displays in a Popup Menu the priority of the Commands in the Device Emulator.
  2. Long Label
    • Comments: The long label is optional. If the long label is not present on a command, the short label is always used.
    1. Null is the default value for Long Label property
    2. To invoke the Long Label Editor by clicking the ellipsis (...) button
    3. The values entered in this text box are used as the property value.
    • EXPECTED RESULT: If the "User Code for Obtaining String" radio button is selected, the property value is used as Java code rather than as a static string. Some Divice Emulators may use the short labels of some commands and the long labels of other commands, and it is allowed to switch between using the short and long label at will.
  3. Type
    1. Command's name is the default value.
    2. The combo box containing theTypes. Select a Type from this drop-down menu.
    3. Run the project
    • EXPECTED RESULT: The application uses the command type to specify the intent of this command. For example, if the application specifies that the command is of type BACK, and if the device has a standard of placing the back operation on a certain soft-button, the implementation can follow the style of the device by using the semantic information as a guide


Test suite: Common Form Items Properties

Purpose:
Setup:

  1. Default Command
    1. Drag&Drop one Command to one specific Form Item.
    2. The value of "Default Command" combobox is "None". Select the new Command from this drop-down menu.
    3. Drag&Drop other different Command to the same Form Item.
    • EXPECTED RESULT: It displays the command in the "Assiged Item Commands" section in the Screen Design.The command or commands should be shown in popup, Menu in the default Device Emulator .
  2. Preferred Size
    • Comments: The value may depend on how the device uses the screen and may be affected by the presence or absence of the ticker, title, or commands.
    1. Invoke the Preferred Size Window by clicking the ellipsis (...) button
    2. Both the preferred width and height are unlocked.
    3. Unlock both boxes.
    4. Change the values and press OK.
    • EXPECTED RESULT: It displays the new size of the FormItem in the Screen Design and Device Emulator.
  3. Label
    1. To invoke the Label Editor by clicking the ellipsis (...) button
    2. The values entered in this text box are used as the property value.
    • EXPECTED RESULT: It display the new label for the Form Item in the Screen Design. If the "User Code for Obtaining String" radio button is selected, the property value is used as Java code rather than as a static string.


Test suite: ChoiceGroup

Purpose:
Setup:

  1. ChoiceGroup Type
    1. The combo box containing all list types. Select a Type from this drop-down menu.
    • EXPECTED RESULT: It displays the new list Type in the Screen Designer. EXCLUSIVE: The radio button specifys the restrictive List Element setting. MULTIPLE : The checkboxes specify other additional List Elements.
  2. ChoiceGroup Fit Policy
    1. TEXT_WRAP_DEFAULT is the Fit Policy's default value.
    2. The combo box containing the Fit policies. Select a Fit Policy from this drop-down menu.
    3. Fill one Choice Element with a long String.
    4. Choose TEXT_WRAP_ON.
    • EXPECTED RESULT: It displays the long String of the Choice Element in two lines, in the Screen Design. If you choose TEXT_WRAP_OFF, it displays the long String of the List Element in one line.


Test suite: DateField

Purpose:
Setup:

  1. Input Mode
    1. The combo box containing all Input Modes. Select a Type from this drop-down menu.
    • EXPECTED RESULT: It displays the Input Mode in the Screen Designer.DATE input mode allows to set only date information and TIME only time information (hours, minutes). DATE_TIME allows to set both clock time and date values.


Test suite: ImageItem

Purpose:
Setup:

  1. Image
    1. Drag&Drop Image Resource to the ImageItem.
    2. To assign the Image Resource at Image Property (combo box).
    • EXPECTED RESULT: If this Image Resource has one Image assigned, it will display the image in the Screen Design. If not follow the Image Resource' steps to assign image.
  2. Alternate Text
    1. To invoke the Alternate Text Editor by clicking the ellipsis (...) button
    2. The values entered in this text box are used as the property value.
    • EXPECTED RESULT: It displays the text string to be used if the image exceeds the devices capacity to display it. If the "User Code for Obtaining String" radio button is selected, the property value is used as Java code rather than as a static string.
  3. Image Appearance
    1. To assign the Image Resource at Image Property (combo box).
    2. The combo box containing all Appearance types. Select a Type from this drop-down menu (PLAIN, HYPERLINK, BUTTON)
    • EXPECTED RESULT: It displays the IMAGE with the specific Appearance in the Screen Design.To provide hyperlink- or button-like behavior, the application should associate a default Command with this StringItem and add an ItemCommandListener to this StringItem.


Test suite: TableItem

Purpose:
Setup:

  1. Table Model
    1. Assign the simpleTableModel Resource at Table Model Property (combo box).
    • EXPECTED RESULT: The simpleTableModel values set will appear in Screen Design and in default Device Emulator.
  2. Headers Font
    • Comments: See "Font Resource".
    1. Assign the Font Resource at Headers Font Property (combo box).
    • EXPECTED RESULT: The Font resource values set will appear in Screen Design and in default Device Emulator.
  3. Title Font
    • Comments: See "Font resource"
    1. Assign one Font Resource at Title Font Property (combo box).
    • EXPECTED RESULT: The Font resource values set will appear in Screen Design and in default Device Emulator.
  4. Values Font
    • Comments: See "Font resource"
    1. Assign one Font Resource at Values Font Property (combo box).
    • EXPECTED RESULT: The Font resource values set will appear in Screen Design and in default Device Emulator.


Test suite: Spacer

Purpose:
Setup:

  1. Minimum Size
    1. To invoke the Minimum Size Window by clicking the ellipsis (...) button
    2. Enter new value for Width - the minimum width in pixels.
    3. Enter new value for Height - the minimum height in pixels.
    4. Enter negative values in the text box .
    • EXPECTED RESULT:It displays the new size in the Screen Design. The minimum size must be zero or greater. If minWidth is greater than the implementation-defined maximum width, the maximum width will be used instead. If minHeight is greater than the implementation-defined maximum height, the maximum height will be used instead. If the value is negative will appear an Error Window. The unlocked preferred width of a Spacer is the same as its current minimum width. Its unlocked preferred height is the same as its current minimum height.


Test suite: StringItem

Purpose:
Setup:

  1. Text
    1. Invoke the Text Editor by clicking the ellipsis (...) button. The Text default value may be null .
    2. The values entered in this text box are used as the property value.
    • EXPECTED RESULT: It displays the new text in the Screen Design. If the "User Code for Obtaining String" radio button is selected, the property value is used as Java code rather than as a static string.
  2. Appearance
    1. The combo box containing all Appearance types. Select a Type from this drop-down menu (PLAIN, HYPERLINK, BUTTON)
    2. To invoke the Text Editor by clicking the ellipsis (...) button and fill the textbox.
    • EXPECTED RESULT: It displays the TEXT with the specific Appearance in the Screen Design. To provide hyperlink- or button-like behavior, the application should associate a default Command with this StringItem and add an ItemCommandListener to this StringItem.
  3. Font
    1. To invoke the Text Editor by clicking the ellipsis (...) button and fill the textbox.
    2. Drag&Drop Font Resource to the StringItem.
    3. To assign the Font Resource at Font Property (combo box).
    4. In the Inspector select Font Properties.
    5. To invoke the Font Window by clicking the ellipsis (...) button.
    • EXPECTED RESULT: A Font's attributes are style, size, and face.


Test suite: TextField

Purpose:
Setup:

  1. MaximumSize
    1. 120 is default value. Change the value.
    2. Enter Decimal Value.
    • EXPECTED RESULT: Returns the maximum size (number of characters) that can be stored in this TextBox. If you enter a Decimal Value have to appear an Error Screen.
  2. Initial InputMode
    1. To invoke the Initial Input Mode Editor by clicking the ellipsis (...) button.
    2. The values entered in this text box.
    • EXPECTED RESULT: The initial input mode is a hint to the implementation. If the implementation cannot provide an input mode that satisfies the applications request, it should use a default input mode.


Test suite: Resources

Purpose:
Setup:

  1. Image Resource
    1. Drag&Drop Image Resource to the ImageItem.
    2. Assign the Image Resource at Image Property (combo box).
    3. Go to Windows Explorer and assign one image at Project' SRC Folder.
    4. In the navigator select Image Properties.
    5. To invoke the Resource Path Window by clicking the ellipsis (...) button.
    6. Select the Image's path and press OK.
    • EXPECTED RESULT: It displays the image in the Screen Design
  2. Font Resource (System)
    • Comments: The default font specifier used to draw Item and Screen contents. FONT_STATIC_TEXT has the value 0. The font specifier used by the implementation to draw text input by a user. FONT_INPUT_TEXT has the value 1.
    1. Drag&Drop Font Resource to the StringItem.
    2. Assign the Font Resource at Font Property (combo box).
    3. In the navigator select Font Properties.
    4. Invoke the Font Window by clicking the ellipsis (...) button.
    5. Radio Button's Default Type have to be checked, and the System Font, Face,Style,Size sections must be unavailable.
    6. Select System radio button.
    7. Radio Button's STATIC_TEXT have to be checked, the Face,Style,Size sections must be unavailable.
    8. Select Radio Button's INPUT_TEXT, the Face,Style,Size sections must be unavailable.
    • {{{1}}}
  3. Font Resource (Custom)
    1. Drag&Drop Font Resource to the StringItem.
    2. Assign the Font Resource at Font Property (combo box).
    3. In the navigator select Font Properties.
    4. Invoke the Font Window by clicking the ellipsis (...) button.
    5. Radio Button's Default Type have to be checked, and the System Font, Face,Style,Size sections must be unavailable.
    6. Select Custom radio button.
    7. The Face,Style,Size sections must be available and the System Font section must be unavailable.
    8. The Radio Buttons System Face and Medium have to be checked by default.
    9. Make differents combinations with the Face Style and Size.
    • EXPECTED RESULT: It displays the Font changes in the StringItem' Text in the Screen Design.
  4. Ticker Resource
    1. Drag&Drop Ticker Resource to one Screen.
    2. Assign the Ticker Resource at Ticker Property (combo box)
    3. In the navigator select Ticker Properties.
    4. To invoke the Ticker Editor by clicking the ellipsis (...) button
    5. The values entered in this text box are used as the property value.
    • EXPECTED RESULT: It displays the new text in the Screen Design. If the "User Code for Obtaining String" radio button is selected, the property value is used as Java code rather than as a static string.
  5. SimpleTableModel
    1. In the navigator select Resources category > Add and Select simpleTableModel.
    2. Invoke simpleTableModel Window by clicking the ellipsis (...) button.
    3. Default value for Columns and Rows is 0. Use Headers box is unchecked.
    4. Press "Add Row", "Remove Row", "Add Column" and "Remove Column" buttons - the number of the Columns and Rows must change accordingly.
    5. Enter values in the table
    6. Check the Use Headers, the Header will appear in the table.
    7. Press Ok button
    • EXPECTED RESULT: The table values have to be set.
  6. SimpleCancellableTask
    1. In the navigator select Resources category > Add > Select SimpleCancellableTask.
    2. Invoke the Invoke SimpleCancellableTask window by clicking the ellipsis (...) button
    3. Message with button "Go to Source" will be displayed. Click on the button.
    • EXPECTED RESULT: The view is set to editor - cursor is on the line with code for the simple task.


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