TS 60 APISupportUpdate1

Revision as of 17:07, 5 November 2009 by Admin (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

APIsupport Update1 Test Specification for

Author: Tomas Musil
Last update: 28.03.2006
Introduction: Please make familiar with basics of developing modules using apisupport. You need to know what is "platform" for which you develop, etc.

Contents


Test suite: Templates in update 1

Purpose: Templates extend functionality of modules, they provide skeletons of code you need for specific actions. You can use one module for all testcases here, but it's recommended to create new module for each testcase. For details of template functionality see apisupport u1 specifications.
Setup: Create new standalone module.


  1. Options panel - miscellaneous panel
    1. Create new options panel template. Create it as new Miscellaneous panel. It means that in options dialog you'll have a new panel under Miscellaneous category. Check if wizard won't let you finish unless everything is properly filled.
    • EXPECTED RESULT: Install your module in target platform and check in Tools
  1. Options panel - primary panel
    1. Create new options panel template. Create it as new as primary panel. It means that in options dialog you'll have a new primary panel with icon. Check if wizard won't let you finish unless everything is properly filled.
    • EXPECTED RESULT: Install your module in target platform and check in Tools
  1. Module installer
    1. Create new module installer template
    2. Add some code into method restored() of created Installer class, e.g. System.out.println("hello");
    • EXPECTED RESULT: Install your module in target platform, and check that in output window is your controll print present.
  1. JavaHelp Help Set
    1. Create new JavaHelp Help Set template.
    • EXPECTED RESULT: Install your module in target platform, and check, if node of your module is present under Help
  1. Update center
    1. Create new update center from template
    • EXPECTED RESULT: Install your module in target platform, and check if you update center is present in Tools



Test suite: New Features in update 1

Purpose: Update 1 extends functionality of API support for 5.0, it offers new useful features and improvements in UI, so that now is module making is again easier. A lot of things now can be done by multiple ways, you can compare to 5.0.
Setup: You need to be a little familiar with things like "module dependency", difference between Apisupport project types, etc, so it's probably good to start with test specifications for API support 5.0 if you don't understand something what is performed here.


  1. Select target JDK
    1. Create new standalone module
    2. Invoke it's properties, select Libaries category.Select other Java platform then the default one. If there's only default java platform present, you have to add a new Java platform using Manage Java Platform button.
    3. Once you have selected other Java Platform, close properties dialog by OK.
    4. Invoke Clean and build on your module, then run it by install it in target platform.
    • EXPECTED RESULT: Module is sucessfully installed in new instance of IDE. Check in Help
  1. Harness selection
    1. Go to Tools | NetBeans Platform Manager.
    2. Add new platform. If you don't have installed any other platform except your running IDE and you don't want to download and install e.g. trunk dev build, you can copy your netbeans dir to another dir-> it will now act as second platform.
    3. Check harness panel of default platform - Harness supplied with IDE must be selected, and other options must be disabled.
    4. Check harness panel of second platform - You can select harness from IDE, harness from second platform, or navigate to location with other harness dir.
    • EXPECTED RESULT: You can select harness, you can use your custom one, where you can override default targets.
  1. Create NBMs in popup on suite
    1. Create FeedReader sample application
    2. Invoke from popup on Feed Reader application suite Create NBMs
    • EXPECTED RESULT: Check that in $FR_DIR/build/updates dir are present all 4 NBMs of FeedReader application
  1. Libraries node
    1. Create new standalone module
    2. On it's libraries node, invoke add module dependency dialog. Add some dependency on NetBeans API (e.g. TopComponent class)
    3. Check if Window System API node is added under Libraries node.
    4. Check if Window System API is also present under Properties | Libraries.
    • EXPECTED RESULT: Check that dependency is mentioned also in $PROJECT_DIR/nbproject/project.xml
  1. Creating modules in suite by popup
    1. Create new module suite
    2. Expand it's node, invoke popup on Modules node. Choose Add new .. to create new module in suite. Check that newly created module appears under Modules node.
    3. Invoke again popup on Modules node. Choose Add new library.. to create new library wrapper in suite. Choose some external JAR to be wrapped. Check that newly created wraper appears under Modules node.
    4. Create new standalone module, and be careful to create it as standalone.
    5. Invoke again popup on suite's Modules node. Choose Add existing.., and navigate to place where you created standalone module in previous step. Add this module to your suite
    • EXPECTED RESULT: You have suite with 3 suite components - 2 modules, and 1 library wrapper. All of them are visible under Modules node.
  1. Move, copy and delete project
    1. Create new standalone module
    2. Move it somewhere in your filesystem, using Move action in it's popup
    3. Copy you module using copy action.
    4. Delete copied project, check Delete also sources.
    • EXPECTED RESULT: All actions were successfully performed. Check that there are no files and dirs left from your deleted copy of module.



Generated: Tue Dec 19 17:13:43 CET 2006

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