Options Dialog Test Specification

Author: Roman Strobl
Version: 5.0
Last update: 31.10.2005
Introduction: This document serves as a testspeciation of the options dialog. The Options dialog was redesigned completely and replaces the old options dialog. The main goals of redesign were improved UI, better usability and especially easier discoverability of indivdual options. Currently both dialogs are present in the IDE, the classic view will be removed in next releases. This testspec focuses on core functionality of new Options dialog. Tests of individual options from additional modules plugged into Options dialog should be included in testspecs for these modules.
Comment:

Table of Contents

• 1. General Options
• 2. Editor Options
• 3. Fonts and Colors
• 4. Keymaps
• 5. Miscellaneous
• 6. Advanced Options

Test suite 1: General Options Purpose: General tests of Options dialog. Setup: Start the IDE. # Test case Description 1 Options Startup Invoke new Options dialog from main menu in Tools | Options. RESULT: Progress bar should be displayed untill new Options dialog is opened. Startup time should be less than 5 secs on standard workstation. 5 categories should be displayed on left and General section should be opened by default. 2 Options After Startup Start the IDE. Right after startup, open new Options dialog from Tools | Options. Click through all sections and tabs of the Options dialog right after startup. RESULT: No exceptions should be thrown. The dialog should look reasonable even if data is not loaded yet. All sections should be accessible. 3 Packages View In general section change Package View to Tree Packages. Click OK to close the Options. In general section change Package View to Flatten Packages. Click OK to close the Options. RESULT: Check if changes are propagated to the Projects view. Click through packages to see if their behaviour changed. 4 Web Browser Try to change web browser to all available options. Open web browser from View | Web Browser. RESULT: www.netbeans.org should appear in all available browsers. Only browsers which are present on your OS should be listed among options. 5 Proxy Settings Try to change proxy settings. Check if web is accessible or not accessible according to the proxy settings change. Go to Tools | Update Center and check if all changes are propagated to Update Center. Change Proxy settings in Update Center and check if changes are propagated properly to Options dialog. RESULT: Settings should persist, no values should be lost. Changes in Options should propagate to Update Center and vice versa. 6 Auto Update Change Auto Update setting to check on every startup and set ask before check to true. Restart IDE. Confirm check and browse the update dialog. Revert settings to the original ones (weekly, don't ask). Restart IDE and check that the update dialog doesn't appear. RESULT: Update dialog should appear in first case. It should not appear in the second case.

Test suite 2: Editor Options Purpose: Setup: # Test case Description 1 Code Folding Try to activate and deactivate folding in general. Try to activate and deactivate various code foldings. Repeatedly open a java file in editor with various options. RESULT: Check if folding is activated and deactivated properly. Check if individual folding settings are propagated to editor. 2 Code Completion Test all code completion options in both activated and deactivated states. RESULT: All changes should be visible when using code completion. 3 Indentation Try to change all of the indentation options. Go to editor and check if all indetation changes are applied (only on new lines). Try to execute the reformat action from context menu. Go back to original settings. Repeat steps 2 and 3. RESULT: Indentation should change on new lines or on whole source for reformat action. No side effects should appear. 4 Code Templates - Adding Try to add a new code template for Java language. Try to add a code template with the same name to check that this is not allowed. Use the code template in editor. RESULT: Adding a new code template should work properly. 5 Code Templates - Deleting Try to delete the code template you defined in previous step. RESULT: The code template should be removed from the list. 6 Code Templates - Editing Try to edit some of the code templates. Check in editor that the changes were saved. RESULT: Changes should be propagated to editor. 7 Code Templates - Different Languages Try to define a code template for a diffent language, e.g. HTML. Verify that this template is not accessible in Java sources. Verify that this template is available in HTML sources. RESULT: Code template should work only in languages for which it is defined. 8 Code Templates - Multiline Try to define a multiline code template, such as an extended for() cycle. Change the template in the Expanded text window. Activate this template in source editor. RESULT: Multiline code template should be displayed properly with correct formatting. 9 Macros - Adding Try to add a new macro for Java language. Try to add a macro with the same name to check that this is not allowed. Use the macro in editor. RESULT: Adding a new macro should work properly. 10 Macros - Deleting Try to delete the macro you defined in previous step. RESULT: The macro should be removed from the list. 11 Macros - Editing Try to edit some of the macros. Check in editor that the changes were saved. RESULT: Changes should be propagated to editor. 12 Macros - Different Languages Try to define a macro for a diffent language, e.g. HTML. Verify that this macro is not accessible in Java sources. Verify that this macro is available in HTML sources. RESULT: Macro should work only in languages for which it is defined.

Test suite 3: Fonts and Colors Purpose: Setup: # Test case Description 1 Java Editor Basic Colors Change the background of Java editor. Change the foreground of Java editor. RESULT: Check the changes in preview. Go to editor to check that new colors are used in java editor. 2 Java Editor Basic Fonts Change the default font size of java editor and font type. RESULT: Check the changes in preview. Go to editor to see if the changes propagated. 3 Java Editor Other Colors Change the foreground and background colors of all categories of Java editor. RESULT: Check the changes in preview. Check the changes in java editor. 4 Java Editor Other Fonts Try to change font size and font type for all categories of java editor. RESULT: Check the changes in preview. Check the changes in java editor. 5 Other Editors Choose randomly various combinations of an editor and a category. Try to change the foreground color, background color, font size, font type and effect for this category. RESULT: Check the changes in preview. Check the changes in the editor. 6 Restoring Changes Try to restore all changes by clicking the Restore button. RESULT: Check that all editors use default fonts and colors. 7 Duplicating a Profile Duplicate the default NetBeans profile to a profile called "My Test". Try to randomly change various fonts & colors settings. Switch back to the default NetBeans profile. Switch to the new profile. Delete the new profile. RESULT: Fonts & colors should be displayed properly in the new profile. When switching there and back no setting should be lost. It should be possible to delete the new profile. 8 Highlighting Try to change all foreground and background colors in the highlighting section. Change the effect randomly few times. RESULT: Check all changes in the java editor. 9 Annotations Try to change all foreground and background colors for annotations. Try to change the effect few times randomly as well. RESULT: Check the java editor to see if all changes propagated.

Test suite 4: Keymaps Purpose: Setup: # Test case Description 1 Creating a New Keymap Profile Create a new Keymap Profile using the Duplicate button. Try to change randomly some of the keybindings. Go back to the original NetBeans profile. RESULT: Creating a new profile should work properly. New shortcuts should work. After switching back the newly defined shortcuts should not work anymore. 2 Deleting and Restoring Try to delete the profile created in last test. Change some of the shortcuts in the NetBeans profile. Revert these changes using the Restore button. RESULT: Deleting should work properly. All changes done in the NetBeans profile should be reverted in step 3. Verify that in the editor. 3 Adding Shortcuts Choose randomly an action from the keymap tree. Set for this action five random shortcuts with combination of Ctrl, Alt, Shift and Key, including already existing shortcuts. Try all these shortcuts from editor to see if the action works. RESULT: All shortcuts should work, except for those which are already used by a different action. 4 Removing Shortcuts Remove all the shortcuts defined in the previous step. Try all these shortcuts in the editor. RESULT: None of the newly defined shortcuts should work. 5 Global vs. Editor Actions Try to change shortcuts of various global actions and various editor actions. Test all these changes in java editor. RESULT: All changes should be propagated.

Test suite 5: Miscellaneous Purpose: Setup: # Test case Description 1 Ant Settings Try to change all of the Ant settings. Verify that all options work as defined. RESULT: All settings should work as expected. 2 Form Settings Try to change all of the Form settings. Verify that all options work as defined. RESULT: All settings should work as expected.

Test suite 6: Advanced Options Purpose: Setup: # Test case Description 1 Switching to Advanced Options Switch to the Advanced Options. Switch back Basic Options. RESULT: No exceptions are thrown, it takes reasonably short time to swith there and back. 2 Advanced Options Settings Try to randomly change some of the settings in the Advanced Options. Choose those which already exist in Basic Options. Check their values in Basic Options. Try to change these values again in Advanced Options. Check their values in Advanced Options. RESULT: All settings should be changed in both Options dialogs.

---

Generated: 2005 10 31 01:56