TS 61 MobilityProjectProperties

Mobility Pack Test Specification for Mobility projects

Author: Lukas Hasik
Version: 1.0
Lastupdate: 30.5.2008
Introduction:

Contents


Test suite: General Project Properties of Mobility Projects

Purpose: Test functionality of Project Properties of Mobility Projects. This should work for any project type
Setup:

  1. Open project Properties
    1. Right click a mobility project
    2. Choose Project Properties
    • EXPECTED RESULT: Project Properties opens
  2. Project Properties > General > Counter
    1. Open Project Properties. Select the General category
    2. Uncheck Automated Application Version Incrementation
    • EXPECTED RESULT: The Application Version Number isn't increased automatically after every deployment of application. User can write it by hand.
  3. Project Properties > Platform > Change Platform Type
    1. Open Project Properties. Select the Platform category
    2. Change the Platform Type from CDC to CLDC (or vise versa). OK
    • EXPECTED RESULT: Project classpath is rescanned. If there are errors (e.g. missing API) then the project/files are badged correctly. List of available devices is updated according to selected platform. Optional packages are updated as well(only for CLDC).
  4. Project Properties > Change Project Platform
    1. Open Project Properties. Select the Platform category
    2. Change the Emulator Platform. OK
    • EXPECTED RESULT: Project classpath is rescanned. If there are errors (e.g. missing API) then the project/files are badged correctly. List of available devices is updated according to selected platform. Optional packages are updated as well.
  5. Project Properties > Change Device
    1. Open Project Properties. Select the Platform category
    2. Change device, OK, run project.
    • EXPECTED RESULT: Correct emulator shows up.
  6. Project Properties > Change Optional packages
    1. Open Project Properties. Select the Platform category
    2. Change the list of selected optional packages, OK
    • EXPECTED RESULT: The classpath is rescanned. If there is a class using missing API then it is correctly badged with compilation error badge.
  7. Project Properties > Build > Compiling
    1. Open Project Properties. Select the Build > Compiling category
    2. User can change encoding of whole project here
    • EXPECTED RESULT: Right encoding is used for project. JAD is always UTF-8
  8. Project Properties > Build > Obfuscating
    1. Open Project Properties. Select the Build > Obfuscating category
    2. Change the obfuscation level to 9
    3. Build the project
    • EXPECTED RESULT: All classes in project are obfuscated according to the selected level.
  9. Project Properties > Build > Creating JAR
    1. Open Project Properties. Select the Build > Creating JAR category
    2. Change the JAD/JAR name, compile
    • EXPECTED RESULT: You can see that jar/jad file name are changed in Files view
  10. Project Properties > Build > Signing
    1. Open Project Properties. Select the Build > Signing category
    2. Check sign distribution checkbox. Compile.
    • EXPECTED RESULT: Application is signed with the keystore during build process.
  11. Project Properties > Build > Generating Javadoc
    1. Open Project Properties. Select the Build > Generating Javadoc category
    2. Provide a Browser Window Title. OK
    3. Choose Generate Javadoc on project node
    • EXPECTED RESULT: Javadoc is generated with correct title.
  12. Project Properties > Running OTA
    1. Open Project Properties. Select the Running category
    2. Select Execute through OTA. OK
    3. Run project
    • EXPECTED RESULT: Project runs in emulator in OTA mode. BUG #117171
  13. Project Properties > Deploying
    1. Open Project Properties. Select the Deploying category
    2. Choose a deployment method from list. Provide all necessary info for the method. OK.
    3. Deploy on project node
    • EXPECTED RESULT: Correct deployment method is used. The deployment is successful if there are no problems e.g. no internet connection/correct password/etc.


Test suite: CLDC/MIDP Project Properties

Purpose: Test functionality of CLDC/MIDP Project Properties
Setup: Have a Mobility CLDC/MIDP project open in IDE.

  1. Application Descriptor tabs
    1. Select Application Descriptor in project properties
    • EXPECTED RESULT: There are following tabs - Attributes, MIDlets, Push Registry, API Permissions
  2. Application Descriptor > Add Attribute
    1. Select Application Descriptor | Attributes tab in project properties
    2. Add new attribute
    • EXPECTED RESULT: If attribute is chosen from combobox then user cannot decide where it will be placed. For custom attributes he can choose JAD/JAR. Check that custom attribute is present in correct place after build of project (in dist dir in Files view).
  3. Application Descriptor > Remove Attribute
    1. Select Application Descriptor | Attributes tab in project properties
    2. Remove an attribute
    • EXPECTED RESULT: Attribute is removed.
  4. Application Descriptor > Remove MIDlet
    1. Select Application Descriptor | MIDlets tab in project properties
    2. Remove a midlet
    • EXPECTED RESULT: MIDlet is removed.
  5. Application Descriptor > Add MIDlet
    1. Select Application Descriptor | MIDlets tab in project properties
    2. Click Add.. button
    3. The Add Midlet dialog provides alll MIDlet classes in project in the MIDlet class combo.
    • EXPECTED RESULT: MIDlet is added to MIDlet suite of this project.
  6. Application Descriptor > Add Push Registry
    1. Select Application Descriptor | Push Registry tab in project properties
    2. Add.., OK
    • EXPECTED RESULT: New Push Registry entry is added. When you compile project then there is MIDlet-Push-1 entry in JAD and jar manifest.
  7. Application Descriptor > Remove Push Registry
    1. Select Application Descriptor | Push Registry tab in project properties
    2. Remove a Push Registry entry
    • EXPECTED RESULT: Push Registry entry is removed.
  8. Application Descriptor > Add API Permissions
    1. Select Application Descriptor | API Permissions tab in project properties
    2. Add.., OK
    • EXPECTED RESULT: New API Permissions entry is added. When you compile project then there is MIDlet-Permissions entry in JAD and jar manifest.
  9. Application Descriptor > Remove API Permissions
    1. Select Application Descriptor | API Permissions tab in project properties
    2. Remove an API Permissions entry
    • EXPECTED RESULT: API Permissions entry is removed.


Test suite: CDC/AGUI Project Properties

Purpose: Test functionality of CDC/AGUI Project Properties
Setup: Have a Mobility CDC project on CDC Toolkit platform open in IDE.

  1. Application Descriptor tabs
    1. Select Application Descriptor in project properties
    • EXPECTED RESULT: There are following tabs - CDC General, SavaJe.

  2. Browse for Main class
    • Setup: Select Running in project properties. Click Browse...
    1. All executable classes are listed in the Browse Main Class dialog
    2. Select a main class. Click Select Main Class.
    3. Run project.
    • EXPECTED RESULT: Selected class runs in emulator.
  3. Browse for Main class > Xlet
    • Setup: Have two xlets in the project. Select Running in project properties. Click Browse...
    1. All executable classes are listed in the Browse Main Class dialog
    2. Check allow execution of multiple xlets check box.
    3. Now you can select more xlet classes. Click Select Main Class.
    4. Run project.
    • EXPECTED RESULT: Selected classes runs in emulator. This type of execution is used for interxlet communication.

NOTE: issue 136182


Test suite: CDC/Ricoh Project Properties

Purpose: Test functionality of CDC/FP Project Properties
Setup: Have a Mobility CDC project on Ricoh platform open in IDE.

  1. Application Descriptor tabs
    1. Select Application Descriptor in project properties
    • EXPECTED RESULT: There are following tabs - CDC General, Ricoh.

  2. Ricoh Advanced
    1. Select Application Descriptor
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