NBPM Test Specification for NetBeans 4.2
Author: Petr Zajac
Last update: 08/01/2005
Introduction: Test specification for Module Suite Wizard, Module Project Wizard and Library Wrapper Module Project
Table of Contents
|
Purpose:
Setup:
Open the Module suite wizard from templates.
| # | Test case [automated] | Description |
| 1 | Invalid suite name | 1.
Type invalid project name using forbidden characters.
|
|
EXPECTED RESULT:
Preventing user from modules suite creation. |
| 2 | Valid suite name | 1.
Type Suite Name
|
|
EXPECTED RESULT:
Valid Suite is created |
| 3 | Change location | 1.
Change location (use typing and/or selecting by Browse button).
|
|
EXPECTED RESULT:
Valid Suite is created |
| 4 | Set As Main project | 1.
The Set As Main project check box is enabled at deafult (enable/disable it)
|
|
EXPECTED RESULT:
Check if the project is either Main Project (enabled) or not (disabled) |
| 5 | Change platform | 1.
Try create project with different netbeans platforms. (the platforms can be added in (Tools|NetBeans platform manager)
|
|
EXPECTED RESULT:
the platform is correctly setted. Check it in created Module suite Properties |
|
|
Purpose:
Setup:
Open Netbeans Module Project Wizard
| # | Test case [automated] | Description |
| 1 | Invalid module name | 1.
Type invalid project name using forbidden characters.
|
|
EXPECTED RESULT:
Preventing user from module creation. |
| 2 | Valid module name | 1.
Type valid Project Name
|
|
EXPECTED RESULT:
Valid Project created |
| 3 | Change location | 1.
Change location (use typing and/or selecting by Browse button).
|
|
EXPECTED RESULT:
Valid project is created |
| 4 | Set As Main project | 1.
The Set As Main project check box is enabled at deafult (enable/disable it)
|
|
EXPECTED RESULT:
Check if the project is either Main Project (enabled) or not (disabled) |
| 5 | Standalone project | 1.
Select standalone project.
|
|
EXPECTED RESULT:
the platform is correctly setted. Check it in created Module Properties. The Netbeans Platform combobox is enabled.
Try it for different platforms |
| 6 | Add to module suite | 1.
Select Add to module suite.
2.
Select a module suite in combobox or add browse it by Browse button
|
|
EXPECTED RESULT:
Module is created and added to module suite. Check it in Module suite properties. |
| 7 | Valid Code Name Base | 1.
Type valid package name to Code Name Base field
|
|
EXPECTED RESULT:
The valid project is created. It contains package with the codebase name. Check the Code Name Base in project properties |
| 8 | Invalid Code Name Base | 1.
Type invalid package name to Code Name base field
|
|
EXPECTED RESULT:
The finish button is disabled. In wizard status line is shown error message |
| 9 | Module display name | 1.
Type valid display name
|
|
EXPECTED RESULT:
The valid project created. Check the display name |
| 10 | Valid localizing bundle | 1.
Type valid localizing bundle name. Default path is in code name base package/Bundle.properties.
|
|
EXPECTED RESULT:
The valid project created. Check the Bundle.properties file |
| 11 | XML layer | 1.
Type valid XML layer file name. The deafault value is code name base package/layer.xml
|
|
EXPECTED RESULT:
The valid project created. Check the layer.xml file. DOCTYPE is:
DOCTYPE filesystem PUBLIC "-//NetBeans//DTD Filesystem 1.1//EN" "http://www.netbeans.org/dtds/filesystem-1_1.dtd
|
|
|
Purpose:
Setup:
Open Netbeans Library Wrapper Module Project Wizard
| # | Test case [automated] | Description |
| 1 | Invalid library file name | 1.
Type invalid library file name
|
|
EXPECTED RESULT:
The Finish and Next button are disabled. |
| 2 | Valid library file name | 1.
Type valid library jar file name
|
|
EXPECTED RESULT:
The valid Library is created. Check xml tags in the project.xml file (Project Metadata in ImportantFiles) :
project|configuration|data|public-packages|package+ contains all packages from jar librar
project|configuration|data|class-path-extension|runtime-relative-path contains ext/"libname".jar
project|configuration|data|class-path-extension|binary-origin contains release/modules/ext/"libname".jar
Check if the library jar is copied to release/modules/ext/"libname".jar in created project.
|
| 3 | Invalid licence file | 1.
Type invalid lisence file to license field.
|
|
EXPECTED RESULT:
The Next button is disabled and error message is shown |
| 4 | Valid license file | 1.
Browse valid licence file
|
|
EXPECTED RESULT:
New project was created.Check the licence in project properties (build|packaging panel). |
| 5 | Name location and Basic module configuration | 1.
Test it in the same way as in Module project.
|
|
EXPECTED RESULT:
The result is the same as in Module project. |
|
Generated: Thu Sep 15 18:02:48 CEST 2005
