TS 60 JSPeditor

JSP Editor Test Specification for NetBeans 6.5

Author: Jindrich Sedek, updates Vladimir Riha
Version: 1.70.153
Last update: 6th September 2012
Introduction: This document contains procedures for testing JSP editor. The module provides syntax highlighting, indentation, code completion, tag matching, various settings and some more functionality in editor.
Comments: The test specification does not cover JSP documents in XML syntax (*.jspx files).

Contents


Test suite: Syntax highlighting

Purpose: This test suite checks that syntax highlighting in JSP editor is correct.
Setup: No preparation is necessary for this test suite.

  1. JSP syntax highlighting
    1. Use File | New Project... to create new Java Web | Web Application project located in your home directory.
    2. Right click Libraries node and select Add Library....
    3. Select JSTL 1.1 library and click Add Library button.
    4. Replace contents of index.jsp with this file and compare the colors with jsp colors specification.
    • {{{1}}}
  1. TAG syntax highlighting
    1. Right click Web Pages node and select New | File/Folder....
    2. Select Web category and Tag File file type and press Next >.
    3. Setup test as Tag File Name and press Finish.
    4. Replace contents of test.tag with this file.
    • EXPECTED RESULT: Tag file editor supports exactly the same syntax color highlighting as JSP editor. See previous test case.


Test suite: Indentation

Purpose: This test suite checks that auto indentation in JSP editor is working correctly.
Setup: No preparation is necessary for this test suite except having web project open with one JSP and one tag file.

  1. Basic indentation
    1. Place the cursor at end of index.jsp or test.tag file and press Enter.
    2. Press Tab and type <a>| where | denotes cursor.
    3. Press Enter again.
    • EXPECTED RESULT: New line is created and cursor inherits column position of text at previous line. In this case it will be one TAB size indented to right.
  1. Reformat code
    1. In both index.jsp or test.tag editors press CTRL+A.
    2. Press Shift+TAB at least 3 times so that whole text is shifted to left.
    3. Right click in editor area and select Format from popup menu.
    • EXPECTED RESULT: The whole source code is reformated according to JSP indentation engine settings. By default, everything inside an element is shifted one TAB to right.
  1. Scriptlets indentation
    1. Type <% somewhere in both index.jsp and test.tag files to create a scriptlet block.
    2. Type if (true) { and press Enter.
    3. Type switch (age) { and press Enter.
    4. Type case 10: and press Enter.
    5. Type a = b; and press Enter.
    6. Type default: and press Enter.
    7. Type sayHello();
    8. Press Arrow Down twice and type %> to close the scriptlet.
    • EXPECTED RESULT: Java code should follow Java indentation engine settings. By default, everything inside { } block or below any line ending with  : character should be shifted one TAB to right. On the other hand pressing } should shift current line to left. Here you can see how it should look like:


Test suite: Code completion

Purpose: This test suite checks that automatic code completion in JSP editor is working correctly.
Setup: No preparation is necessary for this test suite except having web project open with one JSP and one tag file.

  1. Directives
    1. Open index.jsp page and type somewhere in the code <%@ .
    2. Wait 500 ms or press CTRL+Space to invoke code completion.
    3. 3 directives must be offered: include , page and taglib .
    4. Repeat steps 1 and 2 but with test.tag tag file this time.
    • EXPECTED RESULT: 5 directives must be offered in tag files: attribute , include , tag , taglib and variable .
  2. Attributes
    1. Type <%@page | in index.jsp file and invoke code completion.
    2. 13 attributes should be offered initially. Type i which should reduce the list to 5 items including import . Press Enter.
    3. Now you should have <%@page import="|" in the JSP editor.
    4. Repeat steps 1 and 2 in test.tag file with <%@tag | directive.
    • EXPECTED RESULT: Code completion must offer relevant attributes for directives based on file type and context - used attributes are not suggested again. Specifically, autoFlush , buffer , contentType , errorPage , extends , info , isELIgnored , isErrorPage , isThreadSafe , language , pageEncoding and session for page directive and body-content , description , display-name , dynamic-attributes , example , import , isELIgnored , large-icon , language , pageEncoding and small-icon for tag directive.
  1. Values
    1. Type <%@page isELIgnored="|"%> in index.jsp and press CTRL+Space.
    2. Two options false and true will be suggested. Press Enter to select the first one.
    3. Repeat steps 1 and 2 in test.tag file with <%@tag isELIgnored="|"%> .
    • EXPECTED RESULT: Where appropriate (i.e. set of attribute values is limited) these values should be offered by code completion.
  1. Entities
    1. Type & and wait for code completion or press CTRL+Space.
    2. A long list of items will be suggested. Type q character.
    3. This should reduce the list to only 1 suggestion &quot; . Press Enter.
    • {{{1}}}
  1. Custom
    1. Paste following code to JSP/TAG file
    2.  
      <%! void test(){} %>
      <div>Nothing here</div>
       <% t %>
      
    3. Invoke code completion after the "t"
    • EXPECTED RESULT: Function test() is offered in completion list
  2. Page encoding
    1. Type <%@page pageEncoding="|"%> in index.jsp and press CTRL+Space.
    2. List of all known encodings will show up.
    3. Type K }} which reduces the list to KOI8-R }} item only. Press Enter to select it.
    4. Repeat steps 1 and 3 in test.tag file with <%@tag pageEncoding="|"%> .
    • EXPECTED RESULT: Auto completion must suggest all possible character encodings in both JSP and Tag editors.
  1. Import
    1. See #175015 & #195816
    2. Type <%@page import="|"%> in index.jsp and press CTRL+Space.
    3. Four root packages should be offered initially: com , java , javax and org .
    4. Type o , press Enter and type . char.
    5. Now you should have <%@page import="org|"%> . Press CTRL+Space again.
    6. This way use code completion to import e.g. org.xml.sax.SAXException class.
    7. Repeat the same in test.tag file with <%@tag import="|"%> .
    • EXPECTED RESULT: Auto completion must help with selecting any j2se or j2ee package or class as value of import attribute.
  1. Include
    1. Type <%@include file="|"%> in test.tag and press CTRL+Space.
    2. Only two items show up: ../ and test.tag . Type / char.
    3. Completion suggests META-INF/ , WEB-INF/ and index.jsp . Press Enter and CTRL+Space.
    4. Now you should have <%@include file="/META-INF/context.xml|"%>
    5. Repeat the same in index.jsp file with <jsp:include page="|"%> .
    • {{{1}}}
  1. Scriptlets
    1. Type <% String var;var.| somewhere in both index.jsp and test.tag files.
    2. Press CTRL+Space. Appropriate fields and methogs of java.lang.String class must be suggested.
    3. Type  %> <!-- comment --> <% var.| to close the scriptlet and start another one.
    4. Repeat step 2.
    5. Type  %> <% "hello".| and press CTRL+Space again.
    6. Repeat step 2.
    7. Type  %> <% | and press CTRL+Space again.
    • EXPECTED RESULT: Implicit objects application , config , out , page , pageContext , request , response and session will show up. Besides normal Java code completion must be provided inside scriptlets. Declared variables must be available across more scriptlet blocks.
  1. HTML tags
    1. Type < char somewhere in both index.jsp and test.tag files.
    2. Press CTRL+Space to invoke code completion. Type ht which should narrow selection only to 1 item.
    3. Press Enter. This should auto complete <html> tag.
    4. Verify that other HTML tags and their appropriate attributes are available in code completion.
    • EXPECTED RESULT: Code completion offers all HTML tags like <body> , <table> , <form> etc.
  1. JSP tags
    1. Type <jsp:| in index.jsp and press CTRL+Space.
    2. The following JSP tags are offered by default: attribute , body , declaration , directive.page , directive.include , element , expression , fallback , forward , getProperty , include , param , params , plugin , setProperty , text and useBean .
    3. Repeat step 1 in test.tag file editor.
    • EXPECTED RESULT: The same set of JSP tags is offered in tag file editor plus 5 more tags: directive.variable , directive.tag , directive.attribute , doBody and invoke .
  1. Implicit objects
    1. Type <% response.| somewhere in both index.jsp and test.tag files and press CTRL+Space.
    2. Code completion offers relevant fields and methods of javax.servlet.http.HttpServletResponse class.
    3. In both files replace response by session.getSessionContext().| and press CTRL+Space again.
    • EXPECTED RESULT: Code completion offers relevant fields and methods of javax.servlet.http.HttpSessionResponse class.
  1. Java beans
    1. Type <jsp:useBean id="myDate" scope="request" class="I"/> in both index.jsp and test.tag files and press CTRL+Space.
    2. Java packages and classes will be offered. Use code completion to select java.util.Date and finish the tag by "/> .
    3. Type <% myDI and press CTRL+Space.
    4. myDate will be automatically completed. Type . and press CTRL+Space.
    • EXPECTED RESULT: Code completion offers all fields and methods of java.util.Date class.
  1. Declarations
    1. Type <%! in both index.jsp and test.tag files and press CTRL+Space.
    2. Java packages and classes will be offered except implicit objects.
    3. Type void hello() { this. and press CTRL+Space.
    • EXPECTED RESULT: Code completion offers only appropriate fields and methods of servlet i.e. no packages or classes or implicit objects.
  1. Expressions
    1. Type <%= re in both index.jsp and test.tag files and press CTRL+Space.
    2. Both request and response are suggested. Press Enter and type .
    3. Press CTRL+Space to invoke code completion.
    • EXPECTED RESULT: Code completion offers relevant fields and methods of javax.servlet.http.HttpServletRequest class.
  1. Library tags
    1. Right click Web Pages node and select New File/Folder....
    2. Select Web category and Tag Library Descriptor... file type and press Next >.
    3. Setup library as TLD Name and press Finish.
    4. Repeat steps 1 and 2 but select Tag File as file type.
    5. Setup example as Tag File Name and check Add Tag File to Tag Library Descriptor option.
    6. Use Browse button to select WEB-INF/tlds/library.tld as TLD File and push Finish.
    7. In example.tag delete lines 9 and 13 to uncomment declaration of attributes. Press CTRL+S.
    8. Type <%@taglib prefix="ex" uri="/WEB-INF/tlds/library.tld"%> in index.jsp .
    9. Type <exI somewhere below and press CTRL+Space.
    10. It will get expanded to <ex:example . Press Space and CTRL+Space.
    • EXPECTED RESULT: Code completion offers three attributes title , author and price_info declared in example.tag tag file.
  1. Help window
    1. Type <jsp: and press CTRL+Space.
    2. Code completion will show up together with help window. Use arrows to browse through items.
    3. Verify that help window displays appropriate description for selected jsp tag. Press Enter to confirm some (i.e. jsp:useBean)
    4. Move cursor inside the name of the tag (i.e. <jsp:useBeIan...>)
    5. Press CTRL+Shift+Space which will open help window only.
    6. Press CTRL+Arrow Down which will scroll down the contents of help window.
    7. Verify that help window is available for all JSP, custom or HTML tags and their attributes.
    • EXPECTED RESULT: Help window is opened on each code completion invocation or alone if needed. The contents must be scrollable.

Test suite: Code folding

Purpose: This test suite checks that code folding in JSP editor is working correctly.
Setup: No preparation is necessary for this test suite except having web project open with one JSP and one tag file.

  1. Folds creation
    1. Open JSP created in the first test suite.
    2. Type <%! String getBestIDE() {return "NetBeans 4.1"; } %> somewhere into JSP body.
    • EXPECTED RESULT: Code folds must be created for all tags occupying more than one line and JSP/HTML comments. Besides, also each directive/scriptlet/declaration section has one fold.
  1. Folds collapsing
    1. Put cursor somewhere into JSP document and press CTRL+NumPad-.
    2. Verify that current tag fold was collapsed.
    3. Right click editor area and select Code Folds | Collapse Fold from popup menu.
    • EXPECTED RESULT: Code folds must get collapsed/expanded on appropriate demand via shortcut, menu or mouse click. Collapsed fold is represented by + icon and expanded by - icon in the stripe next to line numbers. Besides, collapsed fold is replaced by rectangle with appropriate identification e.g. <%@...%> in case of directives. If user moves mouse over the box, window with content of tag fold is displayed.
                
 
  1. Folds actions
    1. Press CTRL+Shift+NumPad- to collapse all folds in JSP document.
    2. Invoke View | Code Folds | Expand All from main menu to see whole file again.
    3. Right click in editor and choose Code Folds | Collapse All Comments from popup menu.
    • EXPECTED RESULT: All multiline tags or JSP/HTML comments should be collapsed/expanded on appropriate demand.
  }} 

Test suite: Fragments

Purpose: This test suite checks that jsp and tag fragments editing and includes are working correctly.
Setup: No preparation is necessary for this test suite.

  1. New JSP Fragment
    1. Right click Web Pages node and select New | File/Folder....
    2. Select Web category and JSP File file type and press Next >.
    3. Set some file name nad enable Create as a JSP Segment. press _Finish_.
    • EXPECTED RESULT: New *.jspf file should be created.
  1. New Tag Fragment
    1. Right click Web Pages node and select New | File/Folder....
    2. Select Web category and Tag File file type and press Next >.
    3. Set some file name nad enable Create a Segment of a Tag File. press _Finish_.
    • EXPECTED RESULT: New *.tagf file should be created.
  1. Editing
    1. Go throught previous sections (Indentation, Code completion, Code folding, Expression language,...) and verify the functionality in fragments.
    • EXPECTED RESULT: All the editing features should be working in fragments as well as in simple JSP (Tag) file.
  1. web.xml integration
    1. see issue 133702 and 196392
    2. Open _Configuration files_ node in project view on you project.
    3. Open web.xml file.
    4. Select XML view at the open multiview.
    5. Copy this code into root element web-app.
<jsp-config> 
    <jsp-property-group> 
        <url-pattern>*.jsp</url-pattern> 
        <include-prelude>/header.jspf</include-prelude> 
        <include-coda>/footer.jspf</include-coda> 
    </jsp-property-group> 
</jsp-config> 
    1. Create two more jsp fragments called header.jspf, footer.jspf
    2. Replace the content of header.jspf with this code:
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %> 
    1. Create new JSP file. Type this code in it :
      <c:out value="XYZ"/>
      .
    • EXPECTED RESULT: No error should be highlighted in JSP file and c:out tag should be recognized to be from jstl/core library.


Test suite: Embeddedings

Purpose: This test suite checks that embedded CSS style and Javascript can be well edited in JSP.
Setup: No preparation is necessary for this test suite except having web project open.

  1. Creating embedded CSS style
    1. Use File | New File... to create new HTML document in Web Pages location.
    2. Copy whole content of this document into clipboard.
    3. Press CTRL+A in the editor and then click Edit | Paste from main menu.
    4. Editor should replace its content with text from clipboard.
    • EXPECTED RESULT: Code coloring, code folding and code completion should work in the same manner as in CSS specification, no error should be highlighted in the document.
  1. Editing Javascript code
    1. Type into head of the JSP document
      <script> | </script>
      .
    2. Set cursor possition at place of "|".
    3. Start typing function some_name(){ }
    4. Javascript code should get green background. Try code completion and other editing features embedded into JSP code.
    • EXPECTED RESULT: Code coloring, code folding and code completion should work in the same manner as in Javascript specification, no error should be highlighted in the document.


  1. Using java code and EL in embedded CSS style
    1. Use expression language ${} to generate some piece of CSS code. There are already some usages of expression language in the file.
    2. Use java expressions <%= ... %> and java code <% ... %> to generate some pieces of CSS code.
    • EXPECTED RESULT: There should be not any errors and not any warnings for correctly generated CSS code in embedded sections
  1. Using java code and EL in embedded Javascript code
    1. Use expression language ${} to generate some piece of Javascript code. There are already some usages of expression language in the file.
    2. Use java expressions <%= ... %> and java code <% ... %> to generate some pieces of javascript code.
    • EXPECTED RESULT: There should be not any errors and not any warnings for correctly generated javascript code in embedded sections.


Test suite: Miscellaneous

Purpose: This test suite checks that tag matching, hyperlinking and some other small features are working correctly.
Setup: No preparation is necessary for this test suite except having web project open with one JSP and one tag file.

  1. Tag matching
    1. Place cursor behind some opening tag e.g. <head> at line 6.
    2. Matching end tag (at line 8 in this case) should be highlighted in purple color.
    3. Press CTRL + [[ which must move cursor to the </head> closing tag at line 8.
    4. Press CTRL + A and Delete in both index.jsp and text.tag files and type there what you see in the following picture. Verify that matching for all tags and brackets works.
    • {{result|EXPECTED RESULT: When cursor is placed in opening tag, editor highlights corresponding closing tag and vice versa. Besides, it is possible to jump between them via CTRL + [[ shortcut.}}
  1. Hyperlinking
    1. Hold down CTRL key and move your mouse pointer on WEB-INF/web.xml at line 2.
    2. It will change to hyperlink WEB-INF/web.xml . Click it.
    3. Deployment descriptor web.xml will be opened in editor. Switch back to index.jsp .
    4. Type <jsp:forward page="WEB-INF/tags/example.tag"/> somewhere in index.jsp .
    5. Use this new hyperlink to get to example.tag file.
    6. Type <jsp:include page="../../index.jsp"/> somewhere in example.tag .
    7. Use this new hyperlink to get back to index.jsp file.
    8. Hold down CTRL key and move your mouse pointer on ex:example custom tag. Click the hyperlink.
    • EXPECTED RESULT: JSP/Tag editor allows by CTRL key to quickly jump to files referenced in the source.
                
 
  1. Tag hyperlinking
    1. Create tag library descriptor as a new file.
    2. Create new tag file and add the tag file into tag library during new tag file wizard.
    3. Use taglib directive <%@taglib prefix='tglb' uri='new_tag_library' %> to import new tag library into jsp file.
    4. Use your tag file in jsp file:
       <tglb:myTag /> 
      . Verify hyperlink to your tag file source.
    • EXPECTED RESULT: JSP/Tag editor allows by CTRL key to quickly jump to files referenced in the source.
                
 
  1. Abbreviations
    1. Invoke Tools | Options from main menu and select Editor | Code Templates node.
    2. Select JSP in the Language combo box.
    3. Click New, type ext as Abbreviation and click on OK.
    4. Having selected your new abbreviation, type <ex:example title=" as Expanded Text. Push OK to save and to close dialog.
    5. Press Enter to create new line, type ext and press Space.
    6. It is replaced by <ex:example title=" .
    7. Verify that tglb gets expanded to <%@ taglib uri=" .
    • EXPECTED RESULT: Editor allows to use predefined and user specified abbreviations in both index.jsp and test.tag files.
  1. "Line comment/uncomment"
    1. "Set cursor at some line in HTML document and press Ctrl + /. The line should get commented."
    2. "Press Ctrl + / again the line should get uncommented.
    • EXPECTED RESULT: "Line comment should commement/ uncomment the actual cursor line."
  1. "Selection comment/uncomment"
    1. "Select piece of code in HTML file press Ctrl + /. The selection should get commented."
    2. "Set cursor into the commented area and press Ctrl + / . The commented area should get uncommented.
    3. "Create two commented areas. Select code section covering pieces of both of them. Press Ctrl + / . Both sections should get merged.
    • EXPECTED RESULT: "Selection commement / uncomment action should work as intuitively as possible - see Toggle comment spec "
  1. "Select code action"
    1. Set cursor at your some HTML tag. Press Alt + Shift + .. The tag should get selected.
    2. Press Alt + Shift + . for second time. Whole the tag area should get selected
    3. Press Alt + Shift + . for third time. Whole area of the parent tag should get selected.
    4. Press Alt + Shift + ,. The selection should be reduced back to one tag area selection.
    5. Press Alt + Shift + , for second time. The selection should be reduced back just to one tag name selection.
    • EXPECTED RESULT: "The code selection should enalarge and reduce the selection in code blocks."
  1. "HTML Palette"
    1. HTML Palette should be activated automatically after opening JSP file.
    2. Drag some JSP tag on palette, drop it into JSP page.
    3. Customize dialog should appear.
    4. Fill some data in the dialog and press OK button.
    5. The HTML code should be correctly generated at place of drop.
    6. Repeat previous steps with other palette items.
    • EXPECTED RESULT: "The HTML code should be genearated according to choosen item on the palette and according to filled data in the dialog."
  1. "JSP Palette"
    1. JSP Palette should be activated automatically after opening JSP file.
    2. Drag some JSP tag on palette, drop it into JSP page.
    3. Customize dialog should appear.
    4. Fill some data in the dialog and press OK button.
    5. The HTML code should be correctly generated at place of drop.
    6. Repeat previous steps with other palette items.
    • EXPECTED RESULT: "The JSP code should be genearated according to choosen item on the palette and according to filled data in the dialog."

}}

Test suite: Internationalization

Purpose: This test suite checks that it is possible to use national characters in JSP editor.
Setup: No preparation is necessary for this test suite except having web project open with one JSP and one tag file.

  1. Attribute pageEncoding
    1. Type <%@page pageEncoding="ISO-8859-2"%> as the first line in both index.jsp and test.tag .
    2. Extend the page tag with info attribute and use some Czech characters in its value e.g.:
    3. Save the file. Close it and Open again.
    • EXPECTED RESULT: National characters are preserved in JSP file if pageEncoding attribute is set accordingly.
  1. Attribute contentType
    1. Use contentType="text/html;charset=ISO-8859-2" instead of pageEncoding="ISO-8859-2" in both index.jsp and test.tag files.
    2. Do not modify info attribute and Save the file. Close it and Open again.
    • EXPECTED RESULT: National characters are preserved in JSP file if contentType attribute is set accordingly.
  1. Invalid encoding
    1. Replace ISO-8859-2 with ASCII and press CTRL+S.
    2. Warning about possible loss of used characters will show up. Press No.
    3. Change the charset to invalid ASCIII and press CTRL+S again.
    4. Similar warning will show up proposing to save the file using UTF-8 encoding. Press Yes.
    5. Close the file and Open it again.
    6. Question about unknown ASCIII encoding will show up proposing to open file using UTF-8 . Press Yes.
    7. Delete whole contentType attribute with its value but leave the info one with Czech characters. Press CTRL+S.
    8. Similar dialog as in step 4 will open but proposing default ISO-8859-1 encoding this time.
    • EXPECTED RESULT: JSP editor warns user if document contains characters that are not contained in specified encoding. Besides, it suggests to use UTF-8 if unknown charset is declared or ISO-8859-1 if no charset is given at all.


Test suite: Development

Purpose: This test suite checks that it is possible to compile JSP, run it, view its servlet or errors.
Setup: No preparation is necessary for this test suite except having web project open with one JSP and one tag file.

  1. Run JSP
    1. Use File | New File... to create new test.jsp JSP file.
    2. Right click editor area of test.jsp and select Run File.
    • EXPECTED RESULT: The test.jsp file gets compiled, Tomcat is started and once the web application is deployed successfully new browser window opens with Example JSP title and current date printed.
  1. View servlet
    1. Right click on jsp file test.jsp in the Project Window on the righ and select View Servlet.
    • EXPECTED RESULT: Appropriate servlet file opens in editor. In this case it is test_jsp.java located in your home Tomcat subdirectory by default.
  1. Errors reporting
    1. Replace content of test.jsp file with this file. It contains 8 errors in total.
    2. Invoke Build | Compile "test.jsp" from main menu or press F9 key.
    3. Complain about unterminated page tag will show up in the output window. Click the ...WebApplication1/build/web/test.jsp(2,0) link which takes the cursor to line 2.
    4. Correct the error and repeat step 2.
    5. Go after each error and fix it according to hints mentioned in the comment above the error line.
    6. Once you are done with all errors, right click editor area and select Run File.
    • EXPECTED RESULT: JSP editor supports error annotations and compile action offers links to appropriate lines in output window. Errors are displayed in status bar and tooltips on particular lines. In the end browser will open with Example JSP title and current date.


Test suite: Free From Project

  1. Creating free from
    1. Go to Web Freefrom test specification, download attached zip and process first suite to create a web free form project.
    • EXPECTED RESULT: You shoud have some free form project with two jsp files.
  1. Editing
    1. Open index.jsp or time.jsp of the free form project.
    2. Verify syntax coloring as in test suite 1 of this test specification on the open file.
    3. Verify indentation as in test suite 2 of this test specification on the open file.
    4. Verify code completion as in test suite 3 of this test specification on the open file. Pay more attention on test steps: 1 and 6 - 14.
    5. Choose some other functionality described in this test spec and verify it in free form project.
    • EXPECTED RESULT: All the editor functionality shoud work well in free form project as wel as in the standard one.
  1. Tag file
    1. Create a tag file in free form project.
    2. Go through the functionality list of this test spec and do sanity test of it in tag file in free form project.
    • EXPECTED RESULT: All the editor functionality shoud work well in free form project as well as in the standard one.


Test suite: Settings

Purpose: This test suite checks that JSP editor specific settings are working correctly and are persistent.
Setup: No preparation is necessary for this test suite except having web project open with one JSP and one tag file.

  1. Folding switch
    1. Invoke Tools | Options from main menu.
    2. Select Editor tab at the top of the dialog.
    3. Select General node.
    4. Uncheck Use Code Folding option.
    5. Push OK button.
    • EXPECTED RESULT: An extra stripe for folding widgets gets removed and code can't be folded.
  1. Persistence
    1. Invoke Tools | Options from main menu.
    2. Select Editor tab at the top of the dialog.
    3. Select General node.
    4. Uncheck Use Code Folding option.
    5. Push OK button.
    6. Invoke File | Exit from main menu and restart NetBeans.
    7. Repeat steps 1 and 2.
    • EXPECTED RESULT: Both settings are not set to default values i.e. code folding is turned off and its update interval remains as 10000 ms.


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