STS 70 Apisupport

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

Sanity Test Specification for NetBeans Apisupport functionality

Author: Lukas Hasik
Last update: 5/12/2008
Introduction: Test cases for sanity testing of NetBeans apisupport functionality

Contents


Test suite: Modules Suite wizard

Purpose:
Setup: Open the Module suite wizard from templates - "New Project | NetBeans Modules | Module Suite".

  1. Invalid suite name
    1. Type invalid project name using forbidden characters.
    • EXPECTED RESULT: Preventing user from modules suite creation.
  1. Valid suite name
    1. Type Suite Name
    • EXPECTED RESULT: Valid Suite is created


Test suite: Module Project Wizard

Purpose:
Setup: Open Netbeans Module Project Wizard - "New Project | NetBeans Modules | Module"

  1. Invalid module name
    1. Type invalid project name using forbidden characters.
    • EXPECTED RESULT: Preventing user from module creation.
  1. Valid module name
    1. Type valid Project Name
    • EXPECTED RESULT: Valid Project created
  1. 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.


Test suite: Library Wrapper Module Wizard

Purpose:
Setup: Open NetBeans Library Wrapper Module Project Wizard

  1. Invalid library file name
    1. Type invalid library file name
    • EXPECTED RESULT: The Finish and Next button are disabled.
  1. 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



Test suite: NetBeans Platform Manager

Purpose:
Setup: There are no specials steps to configure the NetBeans IDE for testing NBPM.

  1. Add platform
    1. Open NBPM window
    2. Click to Add platform button (the next and finish button is disabled)
    3. Select a root folder of netbeans distribution
    4. (The next and finish button is enabled)
    5. Check the platform name field on the right side)
    6. Click to next button
    7. (The finish button is enabled)
    8. Clear the Platform name field (The finish button is disabled)
    9. Set the platform name "My platform" (The finish button is enabled)
    10. Click to finish button
    • EXPECTED RESULT: The"My platform" was added to platform manager


Test suite: Platforms

Purpose:
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 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 Libraries 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 successfully 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 suplied 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.


Test suite: Action template

Purpose:

  1. create new Action
    1. Create or open some module
    2. In New project wizard, select new action template
    3. Fill in the wizard, create always enabled action, registered somewhere in main menu.
    4. Run module.
    • EXPECTED RESULT: Check if in ide is module properly loaded and action is available in menu.

Test suite: Meta-Inf services browser

Purpose:


  1. Check: Explore META-INF/services (exported and and all) for standalone, module in suite and nb.org module
  2. Add new service from popup of explorer, the service is bold in all services view
  3. Mask service (delete action) - service is striked
  4. Delete registered service
  5. Adding and removing service in META-INF/services folder in sources


%collapsebox

Test suite: Test libraries Node

Purpose:

  1. Check: Libraries node for standalone module, module in a suite, and nb.org module
    1. Add module
    2. Remove module
    3. Add, remove module by editing nbproject/project.xml
  2. Test Library customizer
    1. recursive dependecy checbox
    2. compilation dependency checkbox
    3. Include test module
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