TS 60 ProjectsProperties

Apisupport Properties Test Specification for NetBeans 6.0

Author: Petr Zajac
Last update: 07/24/2007
Introduction: Test specs for Module project, Module suite prperties

Contents 1 Apisupport Properties Test Specification for NetBeans 6.0 1.1 Test suite: APISUPPORT properties

Test suite: APISUPPORT properties

Purpose:
Setup: Show properties for module project. When are all action finished click to ok button.

1. Project folder field
   1. Check the read only project folder field
   • EXPECTED RESULT: Contains the root folder of project

1. Module suiite field
   1. Check the module suite field
   • EXPECTED RESULT: It is :

1. • For standalone module the module Suite field is not present
   • For module in Module suite - contains the suite folder

1. Source level field
   1. Add a javaclass which support jdk1.5 to project
   2. Try compile the projet for different source levels
   • EXPECTED RESULT:

1. • The compilation must fail when is selected the jdk 1.4 source level
   • The compilation pass when is selected the jdk 1.5 source level

1. Change platform
   1. Change platform in libraries panel. Use also Manage platforms Button to customize available platforms.
   • EXPECTED RESULT:

1. • The platform is changed for standalone module.
   • The combo box and Manage Platforms button are disabled when the project is in Module suite

1. Add Module to classpath
   1. Select default platform for module (run ide) in libraries panel
   2. Click to Add button
   3. Select FileSystem API module. Try also Filter field:
      

                classname - LocalFileSystem 

                package name - org.openide.filesystems 

                JAR paths - org-openide-filesystems.jar 

                display name - File System API 

                code base name - org.openide.filesystems 

           
       

1. • EXPECTED RESULT: The module was added to classpath. Create a java class in the project and try add org.openide.LocalFileSystem lfs line to test classpath consintency.

1. Description in add module
   1. Select default platform for module (run ide) in libraries panel
   2. Click to Add button
   3. Select FileSystem API module.
   • EXPECTED RESULT: The description text area contains information about FileSystem API (OpenIDE-Module-Long-Description)

1. Show javadoc in add module
   1. Select default platform for module (run ide) in libraries panel
   2. Click to Add button
   3. Select FileSystem API module.
   4. click to show javadoc in orter to show javadoc for selected module in external browser. The java doc must be present in platform.
   • EXPECTED RESULT: The javadoc for FileSystem module was shown if the javadoc is present in platform. When the javadoc is not present

 	in the platform the Show javadoc button is disabled 
 

1. Remove module
   1. Select a module added by previous testcase (FileSystem API).
   2. Click to remove button
   • EXPECTED RESULT: The module was removed from classpath. Create a java class in the project and try add org.openide.LocalFileSystem lfs line to test classpath consintency

The compilation of the file fails.

1. Edit module dependecy
   1. Add FileSystem API to classpath (use Add Module to classpath testcase)
   2. Select the File System API in libraries panel.
   3. Click to Edit... button
   • EXPECTED RESULT: Code base Name field contains:
     

1. • Code Name Base- org.openide.filesystems
   • JAR - .../platform6/core/org-openide-filesystems.jar
   • Majore release version is empty
   • Specification version is selected and the value is 6.2
   • Include API Packages is selected
   • The packages lsit contains org.openide.filesystems value
   • (Check if Show javadoc button works)

1. Implementation version in edit module
   1. Edit module (see Edit module dependency)
   2. Select the implementation version (The specification version field is disabled)
   • EXPECTED RESULT: Check the project.xml. rund-pendency tag contains empty implementation-version tag

1. Change specification version in edit module
   1. Edit module (see Edit module dependency)
   2. Select specification version radio button
   3. Change the specification version value
   • EXPECTED RESULT: Check the project.xml file. It contains dependecy code-name-base=org.openide.filesystems

1. Release version in edit module
   1. Edit module (see Edit module dependency)
   2. Select specification version radio button
   3. Change the release version value
   • EXPECTED RESULT: Check the project.xml file. It contains dependecy code-name-base=org.openide.filesystems

1. Required tokens in Libraries panel
   1. Add / remove required token to Required token list
   • EXPECTED RESULT: Check it in Module manifest file (OpenIDE-Module-Requires: token1, token2)

1. Display - display name
   1. Change the display name in Display category
   • EXPECTED RESULT: Display name was changed. Check it in Projects View and in Bundle.properties (OpenIDE-Module-Name)

1. Display - Display category
   1. Change the Category. Select variant in como or type new category
   • EXPECTED RESULT: Check it in Bundle.properties (OpenIDE-Module-Display-Category)

1. Display - Short description
   1. Change the Short description
   • EXPECTED RESULT: Check it in Bundle.properties (OpenIDE-Module-Short-Description)

1. Display - Long description
   1. Change the Long Description text area
   • EXPECTED RESULT: Check it in Bundle.properties (OpenIDE-Module-Long-Description)

1. API Versioning - Code Name base
   1. Select the API versioning category
   • EXPECTED RESULT: Check the code name base in project.xml. Value of project

1. API Versioning - Major release version
   1. Type value to major release version (XXX)
   • EXPECTED RESULT: Check it in Important Files

1. API Versioning - Specification version
   1. Type value to specification version
   • EXPECTED RESULT:

1. • Check it in Important Files

1. API Versioning - Implementation Version
   1. type implementtion version
   • EXPECTED RESULT: check it in module manifest

1. API Versioning - Automatical Implementation Version
   1. type implementtion version (Append automaticall impl version field is enabled)
   2. select Append automaticall impl version field
   • EXPECTED RESULT: check it in module manifest, the Specification version was removed from manifest

1. API Versioning - module type
   1. Select module type (Regular, Autoload, Eager)
   • EXPECTED RESULT: Regular Module, Autoload Module, and Eager Module are bound to is.autoload and is.eager in project.properties

1. API Versioning - public packages
   1. Create few packages in module project
   2. Show API persioning panel in project propertis. -> There will be visible only packages which contains at least one class
   3. Try select public packages
   • EXPECTED RESULT: Check the selected public packages in project.xml

1. API Versioning - friends modules
   1. try add few names of friend modules to friend modules list
   2. change some public packages and check
   • EXPECTED RESULT: Check it in project.xml.

1. API Versioning - provided tokens
   1. type some provided tokens to privided tokens field
   • EXPECTED RESULT: check it in manifest file

1. Build - generate debug info
   1. select/unselect generate debug info
   • EXPECTED RESULT: check it in debugger

1. Build - deprecated apis
   1. select/unselect Report uses of deprecated API
   • EXPECTED RESULT: Check it in compilation

1. Build/Packaging - needs restart on install
   1. select/unselect Needs Restart on Install
   2. build NBM for project
   3. install the NBM using update center
   • EXPECTED RESULT: The installation needs/ doesn't need restart of IDE

1. Build/Packaging - Must be installed globally
   1. select Must be installed globally
   2. build NBM
   3. install it using update center
   • EXPECTED RESULT: the module will be copied to installation of ide

1. Build/Packaging - License
   1. browse or type file name in to License field
   • EXPECTED RESULT: The file must exists. You can check the license during installation from NBM

1. Build/Packaging - Homepage
   1. Type homepage url into Homepage field
   • EXPECTED RESULT: Home Page should be a URL (or blank). Bound to nbm.homepage

1. Build/Packaging - Author
   1. Type author name to author field
   • EXPECTED RESULT: Author may be any text (or blank). Bound to nbm.module.author.

1. Build/javadoc - javadoc Title
   1. Type javadoc Title to javadoc title field
   • EXPECTED RESULT: Javadoc Title is bound to javadoc.title. If no packages are marked as public in the API Versioning panel, a warning label should be displayed at the bottom of this panel:

Generated: Tue Dec 19 16:34:59 CET 2006

• This page was last modified on 5 November 2009, at 17:15.
• This page has been accessed 9 times.