TS 70 PluginManager

NetBeans Plugin Manager Test Specification

Author: Jaromir Uhrik
Now supported by: Michael A. Nazarov
Last update: July 02, 2008
Introduction: The Plugin Manager is the implementation of install and update tool in NetBeans IDE that appears in NetBeans since 6.0 M9 build. It covers the functionality that used to be handled by Autoupdate client module in releases prior to NetBeans 6.0. The Plugin Manager provides the update of plugin or a group of plugins available on the Autoupdate server. This document covers the specification of testing features included in the Plugin Manager module. Tests included in this specification should recognize issues contained in the Plugin Manager module as well as they can check the module usability. If it is not pointed up explicitly then installation/update of set of modules containing at least one module "need IDE restart" plugin is assumed.

Contents


Test suite: Proxy Configuration

Purpose: Test if the proxy configuration is working and if Plugin Manager passes these settings.
Setup: Start IDE with clean userdir, invoke main menu Tools|Options (on Mac OS it is in NetBeans|Preferences). The Options dialog appears.


  1. Proxy Settings
    1. Try to change proxy settings in General settings category .
    2. Restart IDE and check Proxy settings.
    • EXPECTED RESULT: Settings should persist, no values should be lost. Changes in Options should propagate to Plugin Manager.
  1. No Proxy
    1. Try to select No Proxy radiobutton in General settings category.
    2. Check if Plugin Manager can access update center according to the proxy settings change.
    3. Restart IDE and check Proxy settings.
    • EXPECTED RESULT: Settings should persist, no values should be lost. Changes in Options should propagate to Plugin Manager - connection must be successful/unsuccessful depending on the network type and settings.
  1. Advanced Proxy Options
    1. Push More... button and check that values from General settings panel propagate to Advanced Proxy Options dialog and vice versa.
    2. Check that No Proxy Host filters masks properly.
    3. Restart IDE and check Proxy settings.
    • EXPECTED RESULT: Proxy settings are persistent and No Proxy Host textfield can define hosts that are not using proxy.


Test suite: General look tests

Purpose: Tests in this suite should discover the main problems with the general look of the Plugin Manager.
Setup: Go to Tools | Plugins).


  1. Plugin Manager dialog default look
    1. Check the dialog display text.
    2. Check the dialog default displayed tab.
    3. Check default selection.
    4. Check Close button.
    • EXPECTED RESULT: The dialog text must be "Plugins" and the default tab must be "Updates" if any available otherwise the default is "Available Plugins". When no available plugins and no updates then "Installed" tab is selected. By default the first line of the list is selected. Close button must be enabled
  1. Stretch and Shrink test
    1. Stretch the window to fullscreen and Check that the Plugin Manager window is stretched.
    2. Shrink the Plugin Manager to its default size
    • EXPECTED RESULT: The window of Plugin Manager look must look like in default state.
  1. Tabs test
    1. Check tabs number and labels.
    2. Check that tab labels "Updates", "Available Plugins" and "Installed" contain the number of available plugins in brackets (if not zero). When plugins are filtered - it means some filter is in "Search" textfield then in brackets there are 2 numbers separated by slash.
    • EXPECTED RESULT: There must be tabs that are named "Updates", "Available Plugins", "Downloaded", "Installed", "Settings".
  1. Search test
    1. Check that the Search tool is in the proper position.
    2. Type to Search tool some text that appears in the description pane on the right side - do it for all tabs.
    • EXPECTED RESULT: The search tool is in the top right corner; the found text appears immediately as highlighted by yellowish.
  1. Close dialog test
    1. Try to close dialog by Escape key on keyboard and by Close button too. Try this action on each of the tabs.
    • EXPECTED RESULT: The plugin manager should disappear immediately without warning.


Test suite: Settings tab

Purpose: Tests in this suite are related to the Settings tab that appears as the last tab of the Plugin Manager.
Setup: Go to Tools | Plugins.


  1. Add Update Provider with default name
    1. Copy the first provider's url to clipboard.
    2. Push Add button to add update provider.
    3. Update Center Customizer appears.
    4. Select URL textfield and paste the url form clipboard there by Ctrl+V (OK button becomes active).
    5. Uncheck the checkbox
    6. Push OK button.
    • EXPECTED RESULT: The new provider appears in the list with the correct url and is unchecked.
  1. Check added update center
    1. Remember the count of Available Plugins
    2. Uncheck the first update center (the number in the tab disappears - when the tab is clicked then the count of Available Plugins is decreased or empty - which means zero - in case that the other update centest contain no plugins)
    3. Set checked the newly added provider
    4. If necessary, switch to Available Plugins tab and push Check for Newest button.
    • EXPECTED RESULT: The count of Available Plugins is the same as remembered number.
  1. Unsuccessfull Add Update Provider with default name
    1. Copy the first provider's url to clipboard.
    2. Push Add button to add update provider.
    3. Update Center Customizer appears.
    4. Select URL textfield and paste the url form clipboard there by Ctrl+V (OK button becomes active).
    • EXPECTED RESULT: The new provider cannot be crated because the one with the same name already exists.
  1. Edit Update Provider
    1. Select the newly created provider.
    2. Push Edit button.
    3. Update Center Customizer appears.
    4. Change both fields (Name and URL) - set to URL field values that are not valid URL.
    5. Change the URL field to url that is not an URL (e.g. www.netbeans.org).
    • EXPECTED RESULT: The OK button is disabled until the URL is valid (www.netbeans.org should not be accepted while http://www.netbeans.org should be accepted).
  1. Cancel removal of Update Provider
    1. Select the update center provider and push Remove button.
    2. The Question dialog (Yes/No dialog) appears
    3. Push No
    • EXPECTED RESULT: The update provider is not removed from the list of providers.
  1. Remove Update Provider
    1. Select the update center provider and push Remove button.
    2. The Question dialog (Yes/No dialog) appears
    3. Push Yes
    • EXPECTED RESULT: The update provider is removed from the list of providers.
  1. Shared directories checkbox check
    1. Check that the "Force install into shared directories" checkbox can be selected and deselected.
    • EXPECTED RESULT: Checkbox is enabled and it is possible to select and deselect it.
  1. Proxy Settings button test
    1. Push the Proxy Settings button.
    2. Check that the Options dialog appears.
    • EXPECTED RESULT: The Options dialog opens in General Settings panel. Close the Options dialog.
  1. Check Period settings
    1. Change the Check Period combo box to "Every Startup".
    2. Restart IDE.
    3. Check that the update center is checked immediately after the start.
    4. Revert settings to its default (Every Week).
    5. Restart IDE.
    6. Change system time to check that periods are counted properly.
    • EXPECTED RESULT: Progress bar must appear when the period ran out.


Test suite: Available Plugins tab

Purpose: Test the components contained in the Available Plugins tab.
Setup: Start IDE with clean userdir, the Plugin Manager window appears and the Available Plugins tab is selected.


  1. Tab label check
    1. Check the name of the tab
    • EXPECTED RESULT: The tab name is Available Plugins and is followed by the number of plugins in parenthesis.
  1. Columns check
    1. There are 4 columns in the table with the list of plugins.
    • EXPECTED RESULT: The names of columns are Install, Name, Category and Source.
  1. Sort check
    1. Try to sort plugins table according to each of the columns.
    • EXPECTED RESULT: The table lines must sort properly, the table cannot be sorted by Install (the column header must contain indication when the table is sorted by it).
  1. Reload Catalog
    1. Push Reload Catalog button that is located in the top left corner.
    • EXPECTED RESULT: The progress bar appears at the bottom of the plugin manager window and disappears during couple of seconds.
  1. Popup menu check
    1. Invoke popup menu and check the available items.
    • EXPECTED RESULT: Popup menu must be available by Shift+F10 and right mouse button. There are 4 items "Check Category "<category>"", "Check All", "Uncheck Category "<category>"" and "Uncheck All".
  1. Check All test
    1. Select checkbox by the one of plugins.
    2. Invoke popup menu and select "Check All" item.
    • EXPECTED RESULT: All checkboxes must be selected.
  1. Uncheck All test
    1. Deselect checkbox by the one of plugins.
    2. Invoke popup menu and select "Uncheck All" item.
    • EXPECTED RESULT: All checkboxes must be deselected.
  1. Check Category test
    1. Select a plugin.
    2. Invoke popup menu and select "Check Category "<category>"" item.
    • EXPECTED RESULT: All plugins with the same category must have checkbox selected.
  1. Unceck Category test
    1. Select all plugins by Check All action
    2. Select a plugin.
    3. Invoke popup menu and select "Uncheck Category <category>" item.
    • EXPECTED RESULT: All plugins are checked except of these that are in the same category with the selected plugin.
  1. Description area test
    1. Go through the list of plugins by arrow up and arrow down.
    • EXPECTED RESULT: The desription area changes its content according to the selected plugin. Check that the description text matches to the selected plugin.
  1. Keyboard selection test
    1. Go through the list of plugins by arrow up and arrow down.
    2. Push the space button on keyboard.
    • EXPECTED RESULT: It causes the toggling selection/deselection of the checkbox .
  1. Install button check
    1. Check the availability of Install button.
    • EXPECTED RESULT: It must be enabled only if some plugin(s) is selected.


Test suite: Updates tab

Purpose: Test the components contained in the Updates tab.
Setup: Start IDE with clean userdir, the Plugin Manager window appears and the Available Plugins tab is selected.


  1. Tab label check
    1. Select Updates tab
    2. Check the name of the tab
    • EXPECTED RESULT: The tab name is Updates and is followed by the number of plugins in parenthesis.
  1. Columns check
    • EXPECTED RESULT: The names of columns are Update, Name, Category.
  1. Sort check
    1. Try to sort plugins table according to each of the columns.
    • EXPECTED RESULT: The table lines must sort properly, the table cannot be sorted by Update (the column header must contain indication when the table is sorted by it).
  1. Reload Catalog
    1. Push Reload Catalog button that is located in the top left corner.
    • EXPECTED RESULT: The progress bar appears at the bottom of the plugin manager window and disappears during couple of seconds.
  1. Popup menu check
    1. Invoke popup menu and check the available items.
    • EXPECTED RESULT: Popup menu must be available by Shift+F10 and right mouse button. There are 4 items "Check All", "Check Category <category>", Uncheck Category <category>" and "Uncheck All".
  1. Check All test
    1. Select checkbox by the one of plugins.
    2. Invoke popup menu and select "Check All" item.
    • EXPECTED RESULT: All checkboxes must be selected.
  1. Uncheck All test
    1. Deselect checkbox by the one of plugins.
    2. Invoke popup menu and select "Uncheck All" item.
    • EXPECTED RESULT: All checkboxes must be deselected.
  1. Description area test
    1. Go through the list of plugins by arrow up and arrow down.
    • EXPECTED RESULT: The desription area changes its content according to the selected plugin. Check that the description text matches to the selected plugin.
  1. Keyboard selection test
    1. Go through the list of plugins by arrow up and arrow down.
    2. Push the space button on keyboard.
    • EXPECTED RESULT: It causes the toggling selection/deselection of the checkbox .
  1. Update button check
    1. Check the availability of Update button.
    • EXPECTED RESULT: It must be enabled only if some plugin(s) is selected.


Test suite: Downloaded tab

Purpose: Test the components contained in the Downloaded tab.
Setup: Start IDE with clean userdir, the Plugin Manager window appears and the Available Plugins tab is selected.


  1. Tab label check
    1. Select Downloaded tab
    2. Check the name of the tab
    • EXPECTED RESULT: The tab name is Downloaded and is followed by the number of plugins in parenthesis (in case that there are any plugins in the container).
  1. Columns check
    1. There are 2 columns in the table with the list of plugins.
    • EXPECTED RESULT: The names of columns are Install, Name.
  1. Add Plugins... cancelation test
    1. Push Add Plugins... button that is located in the top left corner.
    2. Browse the plugin that you have on your disk and cancel the Add Plugins dialog
    • EXPECTED RESULT: The Add Plugins dialog disappears and the Downloaded tab's install list doesn't change (contains no item).
  1. Add Plugins... confirmation test
    1. Push Add Plugin button that is located in the top left corner.
    2. Browse the plugin that you have on your disk and confirm the Add Plugins dialog
    • EXPECTED RESULT: The Add Plugins dialog disappears and the browsed plugin is added to the Downloaded tab's install list.
  1. Add more plugins
    1. Push Add Plugins... button that is located in the top left corner.
    2. Browse the plugins that you have on your disk and confirm the Add Plugins dialog (multiselection must work)
    • EXPECTED RESULT: The Add Plugins dialog disappears and the browsed plugins are all added to the Downloaded tab's install list.
  1. Sort check
    1. Try to sort plugins table according to Name (ascending and descending).
    • EXPECTED RESULT: The table lines must sort properly, the table cannot be sorted by Install (the column header must contain indication when the table is sorted by it).
  1. Remove test
    1. Push Remove button in the description area.
    • EXPECTED RESULT: The plugin disappears immediately from the list. Try to add the plugin back to the list.
  1. Duplicity check
    1. Try to add some plugin to the list which is already contained in the list.
    • EXPECTED RESULT: The plugin appears only once in the list. Dialog appears and informs that the plugin is already there.
  1. Already installed check
    1. Try to add to the list some plugin that has already been installed.
    • EXPECTED RESULT: The information dialog appears and informs that the plugin is already installed.
  1. Install button check
    1. Unselect all plugins in the list.
    • EXPECTED RESULT: The Install button is enabled only in case that at least one plugin in the list has the checkbox selected.
  1. Description area test
    1. Go through the list of plugins by arrow up and arrow down.
    • EXPECTED RESULT: The desription area changes its content according to the selected plugin. Check that the description text matches to the selected plugin.
  1. Keyboard selection test
    1. Go through the list of plugins by arrow up and arrow down.
    2. Push the space button on keyboard.
    • EXPECTED RESULT: It causes the toggling selection/deselection of the checkbox .


Test suite: Installed tab

Purpose: Test the components contained in the Installed tab.
Setup: Start IDE with clean userdir, the Plugin Manager window appears and the Available Plugins tab is selected.


  1. Tab label check
    1. Select Installed tab
    2. Check the name of the tab
    • EXPECTED RESULT: The tab name is Installed and is followed by the number of plugins in parenthesis.
  1. Columns check
    1. There are 4 columns in the table with the list of plugins.
    • EXPECTED RESULT: The names of columns are Uninstall, Name, Category, Active.
  1. Sort check
    1. Try to sort plugins table according to each of the columns.
    • EXPECTED RESULT: The table lines must sort properly, the table cannot be sorted by Uninstall (the column header must contain indication when the table is sorted by it).
  1. Popup menu check
    1. Invoke popup menu and check the available items.
    • EXPECTED RESULT: Popup menu must be available by Shift+F10 and right mouse button. There are 5 items "Activate Category <category>", "Check Category <category>", "Check All", "Uncheck Category <category>" and "Uncheck All".
  1. Check All test
    1. Select checkbox by the one of plugins.
    2. Invoke popup menu and select "Check All" item.
    • EXPECTED RESULT: All checkboxes must be selected.
  1. Uncheck All test
    1. Deselect checkbox by the one of plugins.
    2. Invoke popup menu and select "Uncheck All" item.
    • EXPECTED RESULT: All checkboxes must be deselected.
  1. Description area test
    1. Go through the list of plugins by arrow up and arrow down.
    • EXPECTED RESULT: The desription area changes its content according to the selected plugin. Check that the description text matches to the selected plugin.
  1. Keyboard selection test
    1. Go through the list of plugins by arrow up and arrow down.
    2. Push the space button on keyboard.
    • EXPECTED RESULT: It causes the toggling selection/deselection of the checkbox .
  1. Uninstall button check
    1. Check the availability of Uninstall button.
    • EXPECTED RESULT: It must be enabled only if some plugin(s) is selected.
  1. Deactivate/Activate test
    1. Check the availability of Deactivate/Activate button.
    • EXPECTED RESULT: Activate button must be available in description area for all plugins that are not Autoload or Eager plugins. Deactivate button is available if the plugin is activated and it changes to Activate immediately after its deactivation and after restart of ide (and vice versa(but deactivate appears immediately)).


Test suite: Local Installation

Purpose: Test that the components contained in the Available Plugins tab can be installed to userdir.
Setup: Start IDE with clean userdir, the Plugin Manager window appears and the Available Plugins tab is selected.

  1. Install cancelation test
    1. Select one plugin and try install it - cancel the installation wizard in any step
    • EXPECTED RESULT: Always the installation must be canceled - nothing will be installed.
  2. Single plugin install test
    1. Select one plugin and install it - repeat it for each of the plugins
    • EXPECTED RESULT: Always no dependency problems should be noticed by installer and only the selected plugin will be installed.
  1. Install all plugins at once
    1. Select all plugins and try to install them at once
    • EXPECTED RESULT: No dependency problems should be noticed by installer and all plugins should be installed at once. Assure that in Settings tab there is the "Force install into shared directories" checkbox as unselected.


Test suite: Shared Installation

Purpose: Test that the components contained in the Available Plugins tab can be installed to shared directory.
Setup: Start IDE with clean userdir, the Plugin Manager window appears and the Available Plugins tab is selected. In Settings tab set the "Force install into shared directories" checkbox as selected.

  1. Install cancelation test
    1. Select all plugin and try install it - cancel the installation wizard in any step
    • EXPECTED RESULT: Always the installation must be canceled - nothing will be installed.
  1. Single plugin install test
    1. Select one plugin and install it - repeat it for each of the plugins
    • EXPECTED RESULT: Always no dependency problems should be noticed by installer and only the selected plugin will be installed.
  1. Install all plugins at once
    1. Select all plugins and try to install them at once
    • EXPECTED RESULT: No dependency problems should be noticed by installer and all plugins should be installed at once.


Test suite: Collision tests

archive.zip doesn't exist, not tested Purpose: Check the behavior of plugin manager when multiple versions of the plugin ara available or the plugin is available from multiple locations.
Setup: Start IDE with clean userdir, unzip archive.zip to some $UC_LOCATION. Register all availble update centers (all files with name updates.xml) from archive folder to plugin manager (in Settings tab) so that there appear newly update centers:

-UC1 as file:/$UC_LOCATION/test1/1/updates.xml

-UC2 as file:/$UC_LOCATION/test1/2/updates.xml

-UC3 as file:/$UC_LOCATION/test1/3/updates.xml

-UC4 as file:/$UC_LOCATION/test1/4/updates.xml

-UC5 as file:/$UC_LOCATION/test2/UCs/1/updates.xml

-UC6 as file:/$UC_LOCATION/test2/UCs/2/updates.xml

Leave them all disabled (unchecked).

  1. Single plugin visibility test
    1. Enable UC1
    • EXPECTED RESULT: module_1 of version 1.0 is available.
  1. Higher version visibility test
    1. Enable UC2
    • EXPECTED RESULT: module_1 of version 2.0 is visible instead of 1.0.
  1. Highest version visibility test
    1. Enable UC3
    • EXPECTED RESULT: module_1 of version 3.0 is visible instead of 2.0.
  1. Different source visibility test
    1. Enable UC4
    • EXPECTED RESULT: UC4 contains all 3 versions of the plugin but only module_1 of version 3.0 is visible and in description area on the right there is visible that the source is "Source: UC4" .
  1. Install plugin with low version
    1. Enable UC1 and disable other UCs
    2. Install this module_1 of version 1.0
    • EXPECTED RESULT: module_1 of version 1.0 successfully installs.
  1. Update plugin
    1. Enable UC2 and disable other UCs
    2. It is possible to see the module_1 of version 2.0 in Updates tab
    • EXPECTED RESULT: module_1 of version 2.0 succesfylly replaces plugin with lower version.
  1. Uninstall plugin
    1. Uninstall module_1
    • EXPECTED RESULT: IDE restarts and module_1 disappears from the list of installed. Version 2.0 of the plugin is visible in Available Plugins tab.
  1. Show plugin A 1.0 with dependency
    1. Enable UC5 and disable other UCs
    • EXPECTED RESULT: Plugins A and B of version 1.0 are available.
  1. Install plugin A 1.0 with dependency
    1. Install plugin A
    • EXPECTED RESULT: Plugin B is installed together with A because it depends on it. No plugin A neither B is available then.
  1. Show plugin A 2.0 with dependency
    1. Enable UC6 and disable other UCs
    • EXPECTED RESULT: In Updates there are plugins A and B of version 2.0.
  1. Update plugin A to version 2.0
    1. Update plugin A
    • EXPECTED RESULT: Plugins A 2.0 is installed.
  1. Uninstall B
    1. Uninstall only plugin B
    • EXPECTED RESULT: Plugin A will uninstall as weel. It is because of the dependencies between modules (A depends on B so that existence A without B is not allowed).
  1. Installation A v.1.0 from NBM
    1. Enable only UC5
    2. Add to downloaded tab plugin A (/$UC_LOCATION/test2/NBMs/1/org-yourorgher-a.nbm)
    3. Install plugin A
    • EXPECTED RESULT: Plugin B will be installed too. It will be installed from UC5 - check that in Tools menu there are items "B v1.0 is from UC", "A v1.0 is from NBM".
  1. Unsuccessful add of B v1.0
    1. Add to downloaded tab plugin B (/$UC_LOCATION/test2/NBMs/1/org-yourorgher-b.nbm)
    • EXPECTED RESULT: The dialog appears and tells that it is already installed.
  1. Update from NBM
    1. Add to downloaded tab plugin A v2.0 (/$UC_LOCATION/test2/NBMs/2/org-yourorgher-a.nbm)
    2. Install A from downloaded tab
    • EXPECTED RESULT: A v2.0 is installed from NBMs - check that in Tools menu there are items "B v1.0 is from UC", "A v2.0 is from NBM" (so that B is not updated).
  1. Update from UC
    1. Add to downloaded tab plugin B v2.0 (/$UC_LOCATION/test2/NBMs/2/org-yourorgher-b.nbm)
    2. Enable UC5 and UC6
    3. Install B from Updates tab
    • EXPECTED RESULT: B v2.0 is installed from UC - check that in Tools menu there are items "B v2.0 is from UC", "A v2.0 is from NBM".


Test suite: No permission features

Purpose: Test the behavior of plugin manager when installation was done under admin user and IDE runs under non admin account.
Setup: Install IDE as a root and then run it as a common user. Open Plugin Manager from Tools->Plugins.

  1. Grayed plugins
    1. Select Installed tab of Plugin Manager.
    • EXPECTED RESULT: List of plugins should be gray and it is not possible to uninstall them.
  1. Deactivate plugin
    1. Select any plugin and push Deactivate in its detail panel.
    • EXPECTED RESULT: The plugin is deactivated and the IDE restarts. The red icon appears by the plugin and the Activate button appears instead of Deactivate button - the plugin is still grayed.
  1. Activate plugin
    1. Select deactivated plugin and push Activate button
    • EXPECTED RESULT: The plugin activates and the IDE restarts. The green icon appears back by the plugin and the Deactivate button appears instead of Activate button - the plugin is still grayed.
  1. Install plugin
    1. Select Available Plugins tab and install any plugin
    • EXPECTED RESULT: The plugin is installed and it is not grayed in the Installed tab.
  1. Uninstall currently installed plugin
    1. Select the currently installed plugin in Installed tab and uninstall it
    • EXPECTED RESULT: The plugin uninstalls correctly.
  1. Deactivate installed plugin
    1. Install any plugin and after its installation push Deactivate button in Installed tab
    • EXPECTED RESULT: IDE restarts. By the plugin there appears red icon and the plugin is not grayed.
  1. Activate plugin
    1. Select deactivated plugin and push Activate button
    • EXPECTED RESULT: The plugin activates and the IDE restarts. The green icon appears back by the plugin and the Deactivate button appears instead of Activate button.
  1. Activate plugin
    1. Select deactivated plugin and push Activate button
    • EXPECTED RESULT: The plugin activates and the IDE restarts. The green icon appears back by the plugin and the Deactivate button appears instead of Activate button.
  1. Force install into ide dir
    1. In Settings tab try to enable checkbox "Force install into shared directories"
    • EXPECTED RESULT: The dialog appears that tells that the user doesn't have permitssion to write to the ide dir
  1. Install plugin that goes by default to IDE dir
    1. Select plugin that requires installation to IDE dir and try to install it
    • EXPECTED RESULT: The plugin is installed to userdir because it is not possible to install it to the IDE dire because of missing permission.


Test suite: Run in background

Purpose: Test that the ide is possible to install plugin(s)in bacground. Background installation is the new feature that appeared in builds since the middle of January 2008 (NetBeans 6.1 branch).
Setup: Start IDE with clean userdir, invoke main menu Tools|Plugins.


  1. "Run in Background" checkbox appearance
    1. I "Available Plugins" tab select all content by popup "Check All" and push "Install" button.
    2. Push "Next" and select the license agreement checkbox.
    3. The "Install" button gets enabled so push it.
    4. Check that the checkbox "Run in Background" is available in the installer.
    • EXPECTED RESULT: The checkbox is below the progress bar and it must not be selected when the panel appears. The progress bar in the installer is moving on accordingly.
  1. Run in Background
    1. As a result of previous test case the installer starts installation.
    2. Check the checkbox "Run in Background" enabled.
    • EXPECTED RESULT: The installer disappears and the progress appears on the right of the status bar.
  1. Show Process
    1. Invoke popup menu on the progress and select Show Process item.
    • EXPECTED RESULT: The progress is zoomed and contains information about the current plugin that is being installed.
  1. Cancel Process of installation
    1. In popup menu of progress select Cancel Process item.
    • EXPECTED RESULT: The process of installation is canceled.
  1. Install all content in background
    1. I "Available Plugins" tab select all content by popup "Check All" and push "Install" button.
    2. Push "Next" and select the license agreement checkbox.
    3. The "Install" button gets enabled so push it.
    4. Check that the checkbox "Run in Background" is available in the installer - set it selected.
    • EXPECTED RESULT: The progress informs tha modules are being Downloaded, then Verification is noticed.
  1. Restart icon appearance
    1. After all plugins are downloaded then in the position of progress appears the restart icon with the bubble.
    • EXPECTED RESULT: It apears only if there is a plugin that requires restart of IDE.
  1. Check Restart
    1. Click on the restart icon.
    • EXPECTED RESULT: IDE restarts.


Test suite: Various scenarios

Purpose: Test that some problematic testcases are working (they are here usually as a consequence of some known issue).
Setup: Start IDE with clean userdir, invoke main menu Tools|Plugins.


  1. Postponed install
    1. Let plugin A depends on B and B needs restart.
    2. Install B but at the last panel use radio "Restart IDE Later".
    3. Try to install A.
    • EXPECTED RESULT: The plugin A cannot be installed and the installer informs about it - it tells that the B is waiting to be installed first. The status line of IDE contains restart icon which can be pushed and causes restart of IDE. After the IDE is restarted the plugin A installs smoothly.
  1. Update of updater.jar
    1. Open Plugin Manager and go to the Setting tab and select the main update center (the one that contains declaration of org-netbeans-modules-autoupdate-services.nbm).
    2. Click on the URL on the right that opens proper url in the default web browser (if the browser has troubles with opening then try to delete .gz suffix in browser url).
    3. Create updates.xml file on $YOUR_LOCAL_PATH and paste to this xml first couple of catalog lines - lines before first occurrence of <module> tag.
    4. Paste to the end of catalog following code:
      <license name="license.txt">[NOLICENSESPECIFIED] </license></module_updates>
    5. Find the section which contains string codenamebase="org.netbeans.modules.autoupdate.services".
    6. Copy to clipboard whole <module> tag related to this plugin and paste it to updates.xml
    7. Replace license attribute to license="license.txt"
    8. Replace distribution attribute to distribution="org-netbeans-modules-autoupdate-services.nbm"
    9. Increase the attribute OpenIDE-Module-Specification-Version (+1)
    10. Save the updates.xml
    11. Download the org-netbeans-modules-autoupdate-services.nbm to the $YOUR_LOCAL_PATH
    12. Change all attributes mentioned above also in org-netbeans-modules-autoupdate-services.nbm/Info/info.xml
    13. Change param specversion (+1) in the org-netbeans-modules-autoupdate-services.nbm/netbeans/config/Modules/org-netbeans-modules-autoupdate-services.xml
    14. Increase the attribute OpenIDE-Module-Specification-Version (+1) in org-netbeans-modules-autoupdate-services.nbm/netbeans/modules/org-netbeans-modules-autoupdate-services.jar/META-INF/MANIFEST.MF
    15. Delete org-netbeans-modules-autoupdate-services.nbm/META_INF/NB_IDE.DSA
    16. Delete org-netbeans-modules-autoupdate-services.nbm/META_INF/NB_IDE.SF
    17. Replace org-netbeans-modules-autoupdate-services.nbm/netbeans/modules/ext/updater.jar/org/netbeans/updater/resources/updatesplash.gif by some e.g yellowish .gif file to differentiate its look
    18. Pack the org-netbeans-modules-autoupdate-services.nbm with changes
    19. In IDE dir delete nb6.1/modules/ext/locale/updater_nb.jar (nb6.1 cluster name can have different name according to the NetBeans version)
    20. In Plugin Manager's Settings tab add the update center with url file:///$YOUR_LOCAL_PATH/updates.xml
    21. The update of org-netbeans-modules-autoupdate-services.nbm appears in Updates tab (all other updates disappear from the Updates tab - check this too)
    22. Update the module
    • EXPECTED RESULT: After the restart the splash with the yellowish part appears - it proves that the updater is upgraded. Check the same testcase for the user with admin priviledges but also for user that has no write permissions to the IDE folder (in this case the new updater resides in userdir and is correctly working). Test some another update/install and check that the new updater is used.
  1. Non Kits installed
    1. Install all from Available Plugins tab
    2. Assure that Available Plugins tab is empty
    3. Run IDE with switch -J-Dplugin.manager.modules.only=true
    • EXPECTED RESULT: The Available Plugins tab must be empty (otherwise plugins in this tab don't depend on a kit which is issue).
  1. Bubble Update
    1. Assure that the update via bubble is working
    • EXPECTED RESULT: .
  1. Help
    1. Assure that update via Help|Check for Updates is working
    • EXPECTED RESULT: .
  1. Update all plugins
    1. For this purpose use the File:CatalogUpgrader.jar CatalogUpgrader.jar tool which changes versions in .nbm files and catalogs. Saves all such catalogs together with .nbm files to the specified location.
    2. Register these catalogs and remove original catalogs
    3. Update all plugins
    • EXPECTED RESULT: Assure that all installed plugins have version starting with the prefix e.g. "1000.".
  1. Unistall of updated plugin
    1. Install plugin XYZ version 1.0 as admin
    2. Update to plugin XYZ version 2.0 as non-admin
    3. Uninstall plugin XYZ as non-admin
    4. Plugin XYZ is then in version 1.0 and only admin can uninstall it
    5. Uninstall XYZ as admin
    • EXPECTED RESULT: The plugin is completely uninstalled now.

Test suite: Run on JRE scenarios

Purpose: Since 6.5 it is possible to run IDE on JRE (because some distribution like Ruby don't need full JDK). This suite provides basic test cases that are related to such functionality
Setup: Let's assume that the JRE is installed at $JREPATH


  1. Run javase distribution on JRE
    1. Run javase distribution with the switch --jdkhome $JREPATH
    • EXPECTED RESULT: During the startup the Warning fialog appears and tells that some plugins require JDK packages and must be disabled when running on JRE. Check that in plugin manager these plugins are disabled then. Check that it is not possible to create java projects.
  1. Enable disabled plugins
    1. Try to enable plugins which are disabled as a consequence of previous testcase
    • EXPECTED RESULT: Installer tells that plugins cannot be enabled because running on JRE - the message must properly tell which dependencies are broken.
  1. Run ruby or php distribution on JRE
    1. Run some distribution which don't need JDK with the switch --jdkhome $JREPATH
    • EXPECTED RESULT: The IDE starts without problems.
  1. Install some plugins which require JDK
    1. Try to install a plugins which requires JDK (e.g. apisupport)
    • EXPECTED RESULT: Installer tells that plugins cannot be installed because running on JRE - the message must properly tell which dependencies are broken.

Resources

  1. archive.zip
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