TS 61 ProjectOperations
Operations on NetBeans Module Nodes Test Specification for NetBeans 6.1
Author: Petr Zajac
Last update: 02/01/2008
Introduction:
Contents |
Test suite: Tests Operations on projects and Module suites
Purpose:
Setup:
There is no specials steps to configure ide for this testspecs.
- Build, campilation
- Perform build on your standalone module
- {{result|EXPECTED RESULT: try also :
compile single module
clean
clean and build
- Generate javadoc
- Perform generate javadoc action on netbeans module project
- EXPECTED RESULT:
Module has public package
yes - the javadoc is generated and opened in web browser
no - warning dialog shown
- Run unittest
- Run a unit test :
all units - Test Project action on module project node
simple test
debug simple test
- EXPECTED RESULT: Test is run
- Run standalone module
- Run standalone netbeans module (Run Project action)
- EXPECTED RESULT: Module is started in selected platform.
- Reload standalone module
- The module is already running. Perform Install/Reload module in platfrom action.
- EXPECTED RESULT: The modue is reloaded. It should be tested for example on different implementation if Action
- Debug standalone module
- Perform Debug Project action
- EXPECTED RESULT: Debug is started. Try also:
stop on toggled breakpoint
Apply code change
Step into, Step over, Step out
Watches
Step into code of platfrom when the sources are present in platfrom (look at Tools
- Create nbm
- Perform create nbm on netbeans module project
- EXPECTED RESULT: The nbm file was created in build folder
- Building suite
- Perform build all on module suite
- EXPECTED RESULT: All modules are build in module suite. The module's jars are stored to build/cluster folder
- Run suite
- Perform run on suite
- EXPECTED RESULT: The suite was run. It was used build/testuserdir userdir
- Debug suite
- Perform debug on suite
- EXPECTED RESULT: The suite was run in debug mode. It was used build/testuserdir userdir
- Build nbms
- Perform build nbms on suite (not implemented)
- EXPECTED RESULT: The nbms were built. Check it it build folder.
- Modules node of Suite
- explode Modules suite node
- EXPECTED RESULT: The children consists of modules in suite. Try:
Add Module on module project
Open and Remove module on modules nodes
Test suite: Operations on XML Layer
Purpose:
Setup: Create new module. Modify its layer.xml by adding e.g.new window component (use new file wizard). All actions are invoked subnodes of layer.xml node. This node is found under project node | important files | XML layer | <this layer> As a subnode you can use e.g. Menu node.
- Open Layer Files Action
- Invoke Open layer file(s).
- EXPECTED RESULT: layer.xml file is opened in editor. You should see registration of e.g. menu action etc.
- Pick Icon Action
- invoke Pick Icon..
- browse for some icon
- close the dialog
- EXPECTED RESULT: Icon is registered in layer.xml file. Expand and collapse node (you invoked action on) and you should see the icon.
- Localize Name Action
- Invoke Localize name..
- Type some name
- EXPECTED RESULT: Check if layer.xml contains reference to Bundle and Bundle contains localized name. Name of node where you invoked the action should change.

