TS 60 EditorOptions

Editor - Options Test Specification for 6.0

Author: Max Sauer
Version: 1.1
Last update: 2007/01/24

           This test specification should describe steps needed to throughly test
           functionality of Options Dialog.

Comments:Open a j2se project first.


Test suite: General Settings


  1. Packages view
    1. Select General Tab
    2. Select "View Java Packages as Tree" checkbox
    3. Confirm OD
    • EXPECTED RESULT: Java Packages shown as tree in Explorer's projects view
  1. Default browser
    1. Try to change default browser using combobox in General Tab
    2. Use any link in IDE's Welcome Screen
    • EXPECTED RESULT: Desired Web page should open is selected browser
  1. Default proxy
    1. Verify proxy setting have been imported from system
    • EXPECTED RESULT: This should work for Linux/Gnome & Windows
  1. Manual proxy
    1. Change proxy manually.
    • EXPECTED RESULT: Manual proxy settings should be properly remembered and used ie. in CVS/SVN operations. Check this.
  1. No proxy
    1. Change proxy to "No Proxy"
    • EXPECTED RESULT: No proxy handler should be aviable. Check ie. Welcome screen.
  1. Advanced proxy
    1. Change Advanced Proxy Settings. Verify that these setting are used and remembered.
    • EXPECTED RESULT: Verify last step using Swing Browser. Select in "Web Browser" combo in general Tab.

Test suite: Editor Settings


  1. Editor -- general tab, CF
    1. Turn off Code Folding. Confirm OD.
    2. Try various "Collapse by default" settings.
    • EXPECTED RESULT: Verify that changes were successfully propagated.
  1. Code completion settings
    1. Try various CC settings and combinations.
    2. Confirm OD.
    3. Make some additional changes.
    4. Cancel OD
                   Use CC in opened source file and verify that it behaves correctly,
                   with respect to changes made in step 1.
                   Verify that changes have been canceled in step 4.
  1. Indentation settings
    1. Change "Statement continuation Indent"
    2. Change "Number of spaces per indent"
    3. Change "Expand tabs to spaces" CB. Verify in editor that statements are indented with TABS after Reformat code invocation.
    4. Change "Add leading starts to comments" CB. Verify in editor that javadoc comments have been removed from multiple line javadoc comments, and that they are not added to the beginning of a javadoc multiple line comment when pressing "Enter" .
                   After each change, confirm OD and invoke "Reformat code" inside editor and verify that changes have been applied.
                   Visible changes should be also properly displayed inside "Preview".
  1. Code Templates
    1. Try to add/remove/modify few abbreviations for all Languages from "Languages" combo. Try them in editor. By default, all abbrevs should expand on "Tab" key.
    2. Change value of "Expand Template On" combo, and verify that the change has taken effect.
                   Verify that new abbreviations are saved, and usable in (and only in) desired editor types.
                   Verify that abbreviations are saved between IDE startups.
  1. Macros
    1. Try to define your own Macro. Press "New" button.
    2. Fill in some macro name and "paste-from-clipboard" as macro code, add some shortcut.
    3. Confirm OD
    4. Try the macro inside editor. It should perform desired action, in our case paste from clipboard.
    5. Invoke OD once again. Remove the macro.
    6. Verify that the macro is no longer aviable.
    • EXPECTED RESULT: Macro is functional as expected.

Test suite: Fonts and Colors Settings


  1. City Lights
    1. Switch to City Lights profile
    2. Verify that profile has been previewed
    • EXPECTED RESULT: Profile is properly previewed and selected.
  1. City Ligts modifications
    1. Make some changes to CityLights profile
    2. Do step 1. for multiple Languages/Categories
    3. Change also FG/BG, fonts and effects
                   All changes should be previewed and visible
                   immediately after OD confirmation, at most 1sec. after.
  1. NetBeans Profile
    1. Switch back to 'NetBeans' profile and confirm OD.
    2. Verify that profile has been changed, and nothing became corrupted.
    3. Switch back to CityLights profile.
    4. Verify that no changes made in previous usecase have been lost.
    5. Verify that all changes are persistent between IDE restarts.
    • EXPECTED RESULT: Changes are persistent with respect to profile change and restart.
  1. Highlighting tab
    1. Make some changes inside highlighting tab, both FG and BG
    2. Do this in both color profiles
    • EXPECTED RESULT: All changes were successfully applied and saved
  1. Custom colors
    1. Make some changes inside syntax and highlighting and tab, but this time change on FG/BG colors
    2. Use custom colors this time
    3. Try all three options of setting custom colors (Swatch, HSB and RGB)
    • EXPECTED RESULT: All changes were successfully applied and saved
  1. Inherited colors
    1. Return to OD and change custom colors back to 'Inherited'
    2. Verify that all color combos contain 'Inherited' element
    • EXPECTED RESULT: All color changes have been reverted.
  1. Restore settings
    1. Restore 'NetBeans' profile, confirm OD and verify that everything was rolled back.
    2. Re-invoke OD, switch to City Lights and verify that the changes you have made there were NOT reverted.
    3. Restore 'CityLights' profile, confirm OD and verify that everything was rolled back.
    • EXPECTED RESULT: Everything should be restored.
  1. Duplicate profile 1
    1. Duplicate NetBeans profile, leave the name unchanged
    • EXPECTED RESULT: This should not be allowed. An Error dialog should appear.
  1. Duplicate profile 2
    1. Switch to City Lights profile and make some changes inside both Syntax and Highlighting tabs
    2. Duplicate City Lights profile, this time change the name.
    3. Verify that the changes you have made were transfered to the duplicated profile.
    4. Verify that the 'Restore' button, which is aviable for default profiles, has changed its label to 'Delete'.
    5. Confirm OD
    6. Re-invoke options. Make some changes to the newly created profile.
    7. Verify changes were previewed and confirm OD. Verify that changes have been propagated.
    8. Re-invoke OD and delete profile.
    • EXPECTED RESULT: All actions ended up with expected results.
  1. Annotations tab
    1. Change FG/BG/Wave underline of all elements, subsequently.
    2. Verify that changes are persistent between IDE startups.
    3. Verify that changes affect all profiles.
    • EXPECTED RESULT: All changes were saved and had expected results.

Test suite: Keymap settings


  1. Add shortcut
    1. Open 'Project' node.
    2. Select 'Build main project' node.
    3. Press 'Add' button.
    4. Press 'TAB' button.
    5. Verify that 'TAB' is inserted inside 'Shortcut' text field.
    6. Press Backspace.
    7. Verify that 'TAB' has been deleted from 'Shortcut' text field.
    8. Press Backspace again.
    9. Verify that 'Shortcut already assigned to Delete previous character action' label is shown inside dialog, in red font color.
    10. Verify that 'Clear' button deletes all 'Shortcut' text field content.
    11. Add 'Ctrl-Shift-M' SC to the 'Build Main Project' action.
    12. Confirm OD.
    • EXPECTED RESULT: Verify that the shortcut is functional, ie. 'Ctrl-Shift-M' is building main project.
  1. Remove shortcut
    1. Open 'Project' node.
    2. Remove the shortcut from previous usecase.
    3. Confirm OD.
    • EXPECTED RESULT: Verify that the shortcut is no longer functional.
  1. Switch profile test
    1. Switch to Emacs profile and remember some if its shortcuts.
    2. Confirm OD.
    3. Verify that the Emacs profile is functional.
    4. Go to OD's Indentation tab and turn off 'Expand tabs to spaces' checkbox, confirm.
    5. Verify that Tab key indents source code in the Emacs way. (Tab strike on any caret position indents current line properly, no matter which column the caret stands on)
    6. Try some Emacs shortcuts inside editor.
    7. Add some SC's to Emacs profile and remove some default ones.
    • EXPECTED RESULT: Verify that all changes in SC map took desired effect.
  1. Duplicate profile test
    1. Duplicate 'Emacs' profile. Same name should be forbidden, so think out something else than 'Emacs'.
    2. Add and remove some shortcuts to the newly created profile.
    3. Confirm OD and verify profile being functional.
    4. Re-invoke OD, select 'Emacs' profile and verify the Sc's added to the newly created profile haven't been back ported to the default profiles.
    5. Restart IDE and verify your changes.
                   Both new profile and newly added shortcuts were saved
                   properly and are persistent between IDE sessions.
  1. Delete profile
    1. Verify that the Restore button has changed its label to 'Delete' for the newly created profile.
    2. Delete whole profile, using the button described in step 1).
    3. Verify that the button has changed back to 'Restore' for the default profile and that it works as expected (ie, does not delete them)
    4. Confirm OD.
    5. Re-invoke OD and verify the profile has been successfully deleted.
    • EXPECTED RESULT: Profile has been properly removed.

Generated: Thu Feb 08 11:48:16 CET 2007

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