TS 74 Formatting

Code Formatting Test Specification

Author:Jiri Prox
Version:7.4
Last update:2013/07/24
Introduction: This is test specification for code formatting feature in NetBeans. It covers indentation in editor, reformat action, global formatting settings and project specific formatting settings. The formatting can be customized in several levels. The first level is general formatting respected by all languages. For small set languages there is language specific formatting reflexing the language structure of particular language. This settings overrides the default one. This two level hierarchy can customized also on project level. The project can have it's own formatting settings which has higher priority the the global settings. The customization is made in project properties dialog.

Contents

Test suite: General indentation setting

  1. Number of spaces per indent, right margin
    1. Open options dialog on Options->Editor->Formatting tab.
    2. Select Language: All Languages, Category: Tabs And Indents
    3. Change 'Number Of Space per Indent' and 'Right Margin'
    4. Open all files Indentaiton.{java|html|xml} and reformat them
    • EXPECTED RESULT:The indentation is corrected to specified value, right margin is painted at correct position
  2. Expand tab to spaces, Tab size
    1. Open options dialog on proper tab.
    2. Select Language: All Languages, Category: Tabs And Indents
    3. Change 'Tab Size' and uncheck 'Expand tabs to spaces'
    4. Open all files indentaiton.{java|html|xml} and reformat them
    • EXPECTED RESULT:If there is N spaces in a row (where N is tab size) when invoking reformat, they are replace by one tab character. Tab key does not insert one tab char but tries to add as many tab as it can, a the rest of space to the value of indentation level is filled with spaces. The spaces are never replaced by tab char when typing them manually.
  3. Tabs size, indentation level
    1. Open options dialog on proper tab.
    2. Select Language: All Languages, Category: Tabs And Indents
    3. Change 'Tab Size' and 'Number of Spaces per Indenr' to various values, keep 'Expand tabs to spaces' unchecked
    4. Open all files indentaiton.{java|html|xml} and reformat them after each change
    • EXPECTED RESULT:The spaces and tabs are inserted according to notes in previous test case result. Every time as many spaces as is possible is replaced by tabs, otherwise the spaces are kept in code to get to appropriate indentation level.
  4. Line Wrap - after words
    1. Open options dialog on Editor - > Formatting tab.
    2. Select Language: All Languages, Category: Tabs And Indents
    3. Set Line Wrap to After Words
    4. Open any file and resize the window so the lines are longer than the editor
    • EXPECTED RESULT:The lines are wrapped at the position of the space (or any other word delimiter). At the end on wrapped line there is carriage return sign. Check also the line numbering - the second (and any next) part of line should not have line number.
  5. Line Wrap - anywhere
    1. Open options dialog on Editor - > Formatting tab.
    2. Select Language: All Languages, Category: Tabs And Indents
    3. Set Line Wrap to Anywhere
    4. Open any file and resize the window so the lines are longer than the editor
    • EXPECTED RESULT:The lines are wrapped at the point where the line length exceeds the editor width. The carriage return sign and line numbering are the same as in previous test case

Test suite: Tabs and indents

Purpose: This suite is focused on Java language formatting settings
Setup: Set default formatting setting before performing this suite

  1. Continuation indentation
    1. Open options dialog on proper tab.
    2. Select Language: Java, Category: Tabs And Indents
    3. Change 'Continuation Indentation Size'
    4. Open any java file and type (in scope where it makes sense:
      1. int i = <enter>
      2. public void <enter>
      3. public void metgod(int a, <enter>
      4. class <enter>
      5. int a = 3 <enter>
    • EXPECTED RESULT: The caret is moved to next line. The position of cursot is indentation level + continuation indentation
  2. Label indentation
    1. Open options dialog on proper tab.
    2. Select Language: Java, Category: Tabs And Indents
    3. Change 'Label indentation' and 'Absolute label indentation'
    4. Try another combination of values
    5. Open file Label.java and reformat it
    • EXPECTED RESULT:If 'Absolute indentation' is checked, the label is moved to the 1st colum, othervise it respect indentation level. The 'Label indentaiton' controls additional indentation of the block the label belong to. E.g. the code in block is at position: 'indentation level'*'indentation size'+'label indentation'. If the label indentation is bigger the lable name + 1 for ':' char the blocks is moved to begin at the same line as lable, otherview the block is moved to begin in new line. (Try remaning label to test this)
  3. Indent Top Level Class Members, Indent Case Statements
    1. Open options dialog on proper tab, Language: Java, Category: Tabs And Indents
    2. Uncheck 'Indent Top Level Class Members'
    3. Reformat class Indentation.java
    4. Open options dialog on proper tab, Language: Java, Category: Tabs And Indents
    5. Uncheck 'Indent Case Statement In Switch'
    6. Reformat class Indentation.java
    • EXPECTED RESULT: Whne first checkbox is unselected all class members (methods, fields, inner classes, initializers) are indented to begin at 1st column. (also in inner classes). When second checkbox is unselected the 'case' statements is indented to begin as the same position as related 'switch' statement
  4. Use All Languages Settings
    1. Open options dialog on proper tab, Language: Java, Category: Tabs And Indents
    2. Check 'Use All Languages Settings' and set new values for items which are enabled.
    3. Open Indentation.java and reformat it
    4. Open OD and uncheck 'Override Global Options' again
    • EXPECTED RESULT:The reformat in java respects entered values. Formatting in others files is unchanged. Once the global settings are not overrided the formatting settings is same in all files.

Test suite: Alignment

  1. New lines
    1. Open options dialog on proper tab, Language: Java, Category: Alignment
    2. Check all checkboxes in section New Lines
    3. Open Alignment.java and reformat it
    4. Open OD and uncheck all checboxes again
    • EXPECTED RESULT: New lines are inserted before 'void' in method declaration, else, while, catch and finally. Whne the checkbox are unchecked the newlines are removed again
  2. Multiline Alignment 1
    1. Open options dialog on proper tab, Language: Java, Category: Alignment
    2. Check all checkboxes in 1st column in section Multiline Alignment
    3. Open Alignment2.java and reformat it
    4. Open OD and uncheck all checboxes again
    • EXPECTED RESULT: The parameters in method declaration, arguments in annotations, exceptions behing throws, operands of binary operator , parts of assign statemen are indented that the identifiers stars at the same column. When the checkboxes are unchecked the value of continuation indentation is important again.
  3. Multiline Alignment 2
    1. Open options dialog on proper tab, Language: Java, Category: Alignment
    2. Check all checkboxes in 2st column in section Multiline Alignment
    3. Open Alignment3.java and reformat it
    4. Open OD and uncheck all checboxes again
    • EXPECTED RESULT: The arguments in method call, interfaces behing 'implements', array elements, parts of ternary operator, parts of for statements are indented that the identifiers stars at the same column. When the checkboxes are unchecked the value of continuation indentation is important again.

Test suite: Braces

  1. Position - Class
    1. Open options dialog on proper tab, Language: Java, Category: Braces
    2. In combobox 'Class Declaration' select values
      1. Same line
      2. New line
      3. New line half indented
      4. New line indented
    3. Open BracesPosition.java and reformat it
    • EXPECTED RESULT:The checkbox controls only position of class braces, and the formatting is following 1) opening braces is behind class name, closing is at 1st column, 2) opening brace is at first column at a new line, closing is at 1st column, 3) opening and closing braces are as separated lines, indented by half value of indentation size, 4) opening and closing braces are indented by indentation size
  2. Position - Method
    1. Open options dialog on proper tab, Language: Java, Category: Braces
    2. In combobox 'Method declaration' select values
      1. Same line
      2. New line
      3. New line half indented
      4. New line indented
    3. Open BracesPosition.java and reformat it
    • EXPECTED RESULT: The checkbox controls only position of braces in method declarations, the position is described above
  3. Position - Other
    1. Open options dialog on proper tab, Language: Java, Category: Braces
    2. In combobox 'Other' select values
      1. Same line
      2. New line
      3. New line half indented
      4. New line indented
    3. Open BracesPosition.java and reformat it
    • EXPECTED RESULT:The checkbox controls only position of other types of braces - ifs, initializers, array initializers, block, synchronized blocks, lools, switch, the position where are braces moved is described above
  4. else if
    1. Open options dialog on proper tab, Language: Java, Category: Braces
    2. Uncheck 'Special else if Threatment
    3. Open BracesPosition.java and reformat it
    4. Restore the setting and reformat again
    • EXPECTED RESULT:If check box is selected the else if is not separated into two lines but the code is kept togeather in one line
  5. Brace generation
    1. Open options dialog on proper tab, Language: Java, Category: Braces
    2. In section Braces Generation set folowing values in all comboboxex -
      1. Leave alone
      2. Generate
      3. Eliminate
    3. Open BracesGeneration.java and reformat it after each kind of value is set.
    • EXPECTED RESULT:When 'leave alone' is set, there is not added or removed any braces. When 'generate' is set the bodies of if, while, do while, for is wrapped into a block. See method generate(). If 'eliminate' is set, the body of loops and for are unwrapped from a block if it is possible, e.g. the body contains only one statement. See methods 'eliminate()' and 'cannotEliminate()'

Test suite: Wrapping

Comments: This suite tests the line wrapping, wrapping of each element can by set to 3 level: Never - the code construction is never wrapped, If long - the code is wrapped only if it exceeds right margin, Always - the code is always separated into new lines. To test this follow theses steps 1) open requested file, set mentioned rule to Always and reformat code, 2) undo changes, set right margin to 40 and set wrapping value to If Long, reformat code, 3) undo changes, set wrapping value to Never and reformat 4) set right margin back to 80

  1. Wrapping
    1. Open options dialog on proper tab, Language: Java, Category: Wrapping
    2. Open Wraping1.java
    3. Try each options from the first first half of the rules one by one - from Extend/Implements to Disjunctive Catch Types
    • EXPECTED RESULT:Each type of element is wrapped correctly - either when it exceeds text limit line or when it is set to wrap always. The comment in the source helps to find each element type
           
  1. Wrapping2
    1. Open options dialog on proper tab, Language: Java, Category: Wrapping
    2. Open Wraping2.java
    3. Try each options from the second half of the rules one by one - from For to Wrap After Lambda Arrow
    • EXPECTED RESULT:Each type of element is wrapped correctly - either when it exceeds text limit line or when it is set to wrap always. The comment in the source helps to find each element type

Test suite: Blank lines

Comments: The test suite focuses on controlling number of blank lines between elements in java code. The number of empty spaces between element A and B is the bigger number from blank lines behind A and blank lines before B. The javadoc and inline comments counts as part of related element. The blank lines inside methods body must stay untouched. For the first two test cases set maximum blank lines to some big value

  1. Blank lines
    1. Open options dialog on proper tab, Language: Java, Category: Blank lines
    2. Try change each value one by one
    3. After entering new value, open EmptyLines.java and reformat it
    • EXPECTED RESULT:The number of blank lines respect entered values.
  2. Blank lines - comments
    1. Open EmptyLines.java and add comments - javadoc, block and inline
    2. Open options dialog on proper tab, Language: Java, Category: Blank lines
    3. Try change each value one by one
    4. After entering new value, open EmptyLines.java and reformat it
    • EXPECTED RESULT:The number of blank lines respect entered values. The comment is handled as a part of element
  3. Maximum blank lines - declarations
    1. Set maximum blank line in declaration to some value.
    2. For some of the item in 'Minimum blank lines' set big value (bigger than maximum)
    3. Open EmptyLines.java and reformat it
    • EXPECTED RESULT:The maximum blank lines is respected, there should not be more then maximum blank lines
  4. Maximum blanks lines - code
    1. Set maximum blank lines in code to some value
    2. Open EmptyLines.java
    3. in method body, add more than maximum blank lines between two statements
    4. reformat
    • EXPECTED RESULT:The number of blank line between two statements are reduced to entered maximum

Test suite: Spaces

  1. Spaces
    1. Open ClassA.java
    2. Open options dialog on proper tab, Language: Java, Category: Spaces
    3. Try change each value one by one
    4. After entering new value, reformat ClassA.java
    • EXPECTED RESULT:The spaces are inserted to proper positons

Test suite: Comments

  1. Enable Comments Formatting
    1. Open Comment Formatting setting
    2. Uncheck Enable Comments Formatting
    3. Open comments.Comments class
    4. Reformat Code
    • EXPECTED RESULT: Javadoc is not reformated
  2. Add Leading star
    1. Enable Comments Formatting formatting if is turned off from previous test case
    2. Uncheck all comboboxes (exept the first one - Enable javadoc formatting)
    3. Reformat code
    4. Turn on 'Add Leading Star' and reformat code again
    • EXPECTED RESULT: After the first reformat, all leading stars are removed. After second reformat they are added again
  3. Wrap Text
    1. In formatting settings check 'Wrap text at right margin'
    2. Reformat code
    3. Try chaning position of the right margin and reformat again
    • EXPECTED RESULT: Long lines of javadoc are wrapped.
  4. Wrap one line comments
    1. In formatting settings check 'Wrap Oneline Comments'
    2. Reformat code
    • EXPECTED RESULT: One line comments, e.g. /** some comment*/ are expanded to 3 lines
  5. Preserve New Lines
    1. In formatting settings check 'Preserve blank lines' and 'Wrap text at right margin'
    2. Reformat code
    • EXPECTED RESULT: All new lines are preserved. E.g. when long line is splited into several lines the next line is not pasted just after the end of splitted line but it starts at new line.
  6. Blanks Lines
    1. Check 'Add Blank Line After Description', 'Add Blank Line After Parameter Description' and 'Add Blank Line After Return Tag'
    2. Reformat code
    • EXPECTED RESULT: Each part of javadoc is separated by blank line.
  7. Generate paragraph tag
    1. In formatting setting check 'Generate <p/> On Blanks Lines'
    2. Reformat code
    • EXPECTED RESULT: At each empty line in javadac there is generated <p/> tag
  8. Align
    1. Open comments.Comments class
    2. Reformat javadoc that long lines are separated into several lines
    3. In formatting setting check all three checkboxes starting with 'Allign ... '
    4. Reformat code
    • EXPECTED RESULT: The second and next line of parameter description, return tag description and exception description starts at the same column as the fisrt line

Test suite: Organize Imports

Comments: This suite describe how to use formatting of imports statement.

  1. Use Single Class Imports
    1. In imports formatting setting select 'Use Single Class Import'
    2. Open class imports.Imports
    3. Add some class from another package (for example LinkedList) using code completion
    • EXPECTED RESULT: Correct import of single class is added
  2. Import Inner Classes
    1. In import formatting setting check 'Import Inner Classes'
    2. In class imports.Imports type 'Inner" and from code completino select imports.anotherpackage.AuxClass.Inner class
    3. Delete inserted code (including import)
    4. Turn off 'Import Inner Classes'
    5. Use code completion to insert class 'Inner' again
    • EXPECTED RESULT: In first case 'Inner' is inserted at the cursor position and 'import imports.anotherpackage.AuxClass.Inner;' is added. In the second case the identifier 'AuxClass.Inner" is pasted at the cursor position and 'import imports.anotherpackage.AuxClass;' is added.
  3. Class Count To Use Star Import
    1. In setting set 'Class Count To Use Star Import' to 3
    2. In imports.Count class use import hint to resolve import, one by one
    3. Delete all inserted import and use Fix Imports (ctrl-shift-I)
    4. Delete all imports and all classes from java.util and insert them againg using code completion
    • EXPECTED RESULT: All import are resolved correctly, when inserting 3rd import from the same package the single class imports are replaced by star import
  4. Class Count To Use Star Import - Organize Imports
    1. Open import.Count class
    2. Arrange imports so they do not obey formatting setting - e.g. add more single class imports from java.util
    • EXPECTED RESULT: Organize hint should be provided. After applying it the imports statements are re-arranged according to the setting
  5. Members Count To Use Static Star Import
    1. In settings set Members Count To Use Static Star Import to 3
    2. Open class imports.Count
    3. Use Organize Impoets Hint
    • EXPECTED RESULT: Static imports are replaced by one static star import
  6. Disabled counts
    1. In settings set uncheck the checkboxes next to Members Count To Use Static Star Import and Class Count to Use Star Imports
    2. Open class imports.Count
    3. Reformat the file
    • EXPECTED RESULT:Now the imports are not changed to star imports any more, regardless of their count
  7. Packages To Use Star Import
    1. In setting add one row to table "Packages To Use Star Import", containing package 'java.io' (ckeck box should by checked)
    2. In imports.Imports use code completion to add line File f;
    3. Delete inserted code, go back to formatting setting and uncheck the 'star' column in the table and repeat previous step
    • EXPECTED RESULT: When the start checkbox is checked, the star import is used, even when there is single import from the given package
  8. Use Package Imports
    1. In import formatting setting set 'Use Package Imports'
    2. Use code completion to insert some class
    3. Try fix imports, import hint
    4. Open class where simple class imports are use and use Optimize Imports hint
    • EXPECTED RESULT: Always star import is generated
  9. Use FQN
    1. In import formatting setting set 'Use Fully Qualified Names'
    2. Use code completion to add filed File f; into the code
    • EXPECTED RESULT: When completing identifier File the fully qualified name is inserted (and no import)
  10. Imports Layout
    1. In formatting setting select 'Use Single Class Imports' and increase both 'Count ...'
    2. Modify 'Inport Layout table' so it contains following items (in this order): java.util, all other imports, java.io. Separate Statis Imports is unchecked
    3. Open class imports.Layout and use Organize Imports hint
    • EXPECTED RESULT: The imports are rearranged accoring to the given order
  11. Imports Layout - Separate Static Imports
    1. Open Formatting Setting and check 'Separate Static Imports'
    2. Modify the table so it contains: java.io (static), java.util, all other imports, java.io, all other imports (static)
    3. In imports.Layout use Organize Import hint
    • EXPECTED RESULT: The imports are rearranged accoring to the given order
  12. Imports Layout - Separate Groups
    1. In setting check 'Separate Groups'
    2. Use Organise Imports hints in imports.Layout
    • EXPECTED RESULT: Each group (related to single item in layout table) is separated by blank line

Test suite: Naming

  1. Prefix and Suffix - introduce
    1. Open Formating Options, language: Java, category:Naming
    2. Fill in all prefixed and suffixes
    3. In editor open Naming.java
    4. Select 4 in staticMethod and method and introduce field, variable and parameter
    • EXPECTED RESULT:The automatically generated name in the introduce dialog respect the settings
  2. Prefix and suffix - hints
    1. In editor type usage of non-existing method (e.g. doesNotExist("");)
    2. Use hint to create the method
    • EXPECTED RESULT:The method is created, the parameters has correct names
  3. Prefix and suffix - code completion
    1. In editor create new field, its name should start with prefix for filed and end with suffix (e.g. it the field prefix is set to f and suffix to F then the name should be fNumberF etc...)
    2. in editor type set and use code completion to generate setter
    3. in editor type get and use code completion to generate getter
    • EXPECTED RESULT:The getter and setter is generated correctly, the field name is used without prefix (setNumber and getNumber is generated), the parameter for setter has correct prefix and suffix
  4. Prefix and suffix - suggested names
    1. In editor start typing field "Number and use code completion to suggest name
    2. In editor start typing static field "static Number and use code completion to suggest name
    3. In editor start typing method "public void newMethod(String and use code completion to suggest parameter name
    4. In editor start typing local variable "Number and use code completion to suggest name
    • EXPECTED RESULT:In all cases suggested names has correct prefix and suffix
  5. Prefix and suffix - generate code
    1. Use Generate Code feature (alt-Insert) to generate getter&setters and to generate new bound vetoable property
    • EXPECTED RESULT:All generated fields, variable and parameters has correct prefixes and suffixes
  6. Use Is for Boolean
    1. In Formating Options, language: Java, category:Naming select check box Use Is for Boolean Getters
    2. In editor type new Boolean field (Boolean field;)
    3. Use code completion to generate getter
    4. Use Generate Code to generate getter
    • EXPECTED RESULT:Getter uses is instead of get like for boolean field.

Test suite: Ordering

  1. Members Sort Order
    1. Open options dialog on proper tab, Language: Java, Category: Ordering
    2. Customize element ordering in Members Sort Order
    3. Open Test class and use hints in method method1() to generate missing elements
    • EXPECTED RESULT:Elements order must match predefined order
  2. Sort by visibility
    1. Open options dialog on proper tab, Language: Java, Category: Code Generating
    2. Check Sort Members By Visibility and customize the visibility order
    3. Use hints in Test class, method method2() to verify the code generating
    • EXPECTED RESULT:Elements are inserted at proper position according their visibility modifier
  3. Insertion Point - Caret Location
    1. Open options dialog on proper tab, Language: Java, Category: Code Generating
    2. Set Insertion Point to Caret Location
    3. Open SortOrder class
    4. User Insert Code feature to verify the code generation
    • EXPECTED RESULT:Code is always inserted at the caret location
  4. Insertion Point - Last In Category
    1. Open options dialog on proper tab, Language: Java, Category: Code Generating
    2. Set Insertion Point to Last In Category
    3. Open SortOrder class and user Insert Code feature to verify the code generation
    • EXPECTED RESULT:Code is always generated behind the last element of the given type
  5. Insertion Point - First In Category
    1. Open options dialog on proper tab, Language: Java, Category: Code Generating
    2. Set Insertion Point to First In Category
    3. Open SortOrder class and user Insert Code feature to verify the code generation
    • EXPECTED RESULT:Code is always generated before the first element of the given type
  6. Alphabet
    1. Open options dialog on proper tab, Language: Java, Category: Ordering
    2. Select Sort Members in Groups Alphabetically
    3. Open Alphabet.java
    4. Call Organize members
    • EXPECTED RESULT:The fields and methods are sorted. At first there are field (a,b,c) the getters (getA, getB, isC) and at last the setters (setA,setB, setC)
  7. Keep getter and setters together
    1. Open options dialog on proper tab, Language: Java, Category: Ordering
    2. Select Keep Getters and Setters Together and Sort Members in Groups Alphabetically
    3. Open Alphabet.java
    4. Call Organize members
    • EXPECTED RESULT:The setters and getters are ordered by alphabet but setter and getter are not separated. The order of methods is: getA, setA, getB, setB, isC, setC

Test suite: Per-project formatting

Purpose: This tests formatting setting which applies only to one specific projects. This settings can be compiled among the projects
Setup: Start IDE with default formatting settings (clear userdir) and create new J2se project

  1. Formatting
    1. Open project properties
    2. Select tab formatting
    3. Select 'Use project specific options'
    4. Customize the formatting setting is this dialog
    5. Confirm and reformat source code
    • EXPECTED RESULT: The project formatting is changed. It effects only files in this project. Other files are unchanged. The formatting settings are written to project.properties as a set of properties which differs from the default setting.
  2. Formatting - setting to default
    1. Open project properties
    2. Open project properties
    3. Select tab formatting
    4. Select 'Use global setting'
    5. Confirm and reformat code
    • EXPECTED RESULT: The sources are formatted according to default setting. A prompt dialog appears when 'Use global settings' is selected. Formatting settings are removed form project.properties
  3. Copy formatting setting
    1. Open project properties and customize project specific formatting
    2. Create new project
    3. Go to project properties, formatting tab
    4. Select 'Use project specific formatting' and press 'Load from other project'
    5. In the dialog select first project and confirm
    • EXPECTED RESULT: The settings are copied from the original project to the actual one.
  4. Invalid copy
    1. Repeat previous test case, but in the last step select project without project specific formatting
    • EXPECTED RESULT:A warning appears after selection of project, informing that there are no project specific formatting available
  5. Go to global setting
    1. Open project properties
    2. Select tab formatting
    3. Press 'Edit global options'
    • EXPECTED RESULT: Options dialog is opened with preselected Editor -> Formatting category

Test suite: Format Action

Purpose: This test suite tests several ways of invocation Reformat action

  1. Format Whole File
    1. Open action.WholeFile
    2. Put cursor in the editor and call reformat action
    • EXPECTED RESULT:The content of the file is reformat according the setting - this does not include Organize Imports or Organize Members. This action needs to be called explicitly.
  2. Format Selected Part of File
    1. Open action.PartOfFile
    2. Select lines 13 - 16
    3. Call Reformat Action
    • EXPECTED RESULT:The select part of code is reformated. The indentation is related to previous part of code (see that the method declaration is indented too much)
  3. Format Whole Projects
    1. Select single or more project in Project View
    2. Call Reformat action
    • EXPECTED RESULT:The whole project or projects are reformated. This action may take long time - so there is dialog with progress bar and information which file is beeing actually processed.

Test suite: Export Settings

Purpose: This test suite covers import/export of formatting setting

  1. Full Export
    1. Change formatting settings
    2. Open Options
    3. Click on Export
    4. In the tree check whole Formatting branch
    5. Specify the target file and click OK
    • EXPECTED RESULT:The zip file containing configuration .xml files is created
  2. Partial Export
    1. Repeat previous test case, but not check whole branch, but only some subbranches (e.g. java)
    • EXPECTED RESULT:The generated zip files contains only config xml related to selected subbranch (the content of zip file can by verified during import)
  3. Full Import
    1. Open Options
    2. Click on Import
    3. Select the file created during export
    4. Check all branches and confirm by OK
    • EXPECTED RESULT:The file is imported, the setting in Options dialog are changed
  4. Partial Import
    1. Repeat previous testcase, but import only some subbranch
    • EXPECTED RESULT:Only selected data are imported
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