Author: Emanuel Hucka
Version: 1.2
Last update: 2005/01/25
Introduction: Java with the Editor module offer full support to work with Java sources and structures. Features in Java module are mostly built on JavaHierarchy. JavaHierarchy is created from Java Model provided by modules JMI and Javacore.
Changed sources are reparsed and Java Model is changed after the source files are saved or after parser delay time.
Java model content could be checked via JavaHierarchy in explorers (Project or File views) or in Editor navigation toolbar.
Comment:
Purpose: Check creation of fields, methods, classes, interfaces, constructors and initializers.
Setup:
#
Test case
Description
1
New Initializer
Setup: Create a class from template into a source package of opened project.
Create New Initializer using popup. No dialog is invoked, only static Initialzer is inserted.
RESULT:
New static initializer is created into a class.
2
New Field
Setup: Create a class from template into a source package of opened project.
Create a field into a class using popup menu Add | Field (invoked on ClassElement) or Add Field (invoked on Fields group). This will invoke Field Customizer.
Set field's properties and create it.
Select the new field in a view and invoke action Open on it.
Try also invalid names (*, a-a etc...) -> You would get some Error (Specified name is not a valid Java identifier).
RESULT:
New field is created into the class
3
New Constructor
Setup: Create a class from template into a source package of opened project.
As New Method, but Name, Type, Return Type and Modifiers are disabled.
RESULT:
New constructor is created into a class.
4
New Method
Setup: Create a class from template into a source package of opened project.
Create a method into a class using popup menu Add | Method (invoked on ClassElement) or Add Method (invoked on Methods group).
Try to open the new method in source editor (invoke action Open or double click on it in a view).
Try also invalid names (*, if,a-a etc...)
RESULT:
New method is created into the class.
5
New Inner Elements
Setup: Create a class from template into a source package of opened project.
Create Inner Class, Interface, Enumeration and Annotation type using popup menu Add | Inner ... (invoked on ClassElement).
Try to check their code by invoking Open action.
Try to create Inner Class in just created Inner Class.
RESULT:
New class/interface is created into a class.
6
New top-level elements
You can also create classes, interfaces, enumerations and annotation types in existing .java file (not inner ones).
Try to create class Test.
Using popup on java node (Add|Class..) try to create class Test2. Test2 will be created in file Test.java.
RESULT:
Test.java is created. There are two top-level classes in it: Test and Test2. Test2 cannot be public.
7
Order of elements
Order of java elements in java class node is following:
inner classes, enumerations, annotation types
inner interfaces
group Fields
group Constructors
group Methods
RESULT:
Order of java elements.
To test JDK 1.5 specific elements change platform of work project to jdk 1.5 or higher.
Purpose: This suite checks, if java hierarchy is correctly updated after modifications.
Setup: Create a new class JavaSourceObject into source packages of an opened project.
#
Test case
Description
1
Creating Inner Classes
Write Inner Class into JavaSourceObject class: Open class in Editor and write inner class with at least one method an one field.
Check JavaHierarchy if correspond to source. Examine properties of all made nodes (class, method, field). Make some experiments: change modifiers etc.
Try also make inner class in inner class.
RESULT:
New inner class nodes appear in explorer
2
Creating Inner Interface
Write Inner Interface do the same as in "Creating Inner Classes".
RESULT:
New inner interface nodes appear in explorer
3
Create Outer Class in existing .java file
Write new outer class into JavaSourceObject class: Open class in Editor and write new class at the end of the file.
RESULT:
New class node appears in explorer.
4
Create Outer Interface in existing .java file
Write new outer interface into JavaSourceObject class: Open class in Editor and write outer interface at the end of the file.
RESULT:
New interface node appears in explorer
5
Creating Constructor
Create constructor into JavaSourceObject class: Open class in Editor and write new constructor with at least one argument.
RESULT:
New constructor node appears in explorer.
6
Creating Initializer
Create Initializer: add static{} statement to body of class.
RESULT:
New initializer appears in Constructors group
7
Create new fields and methods
Edit source code of class JavaSourceObject: write method and field. Check if JavaHierarchy is updated correctly. Check your new method by examining properities.
Try to do some changes in source and look if relevant properities are updated: Try to change method's or field's names modifiers, parameters.
Check behavior in nonsense modifiers (e.g. abstract final).
RESULT:
New method and field node appears in explorer
To test JDK 1.5 specific elements change platform of work project to jdk 1.5 or higher.
Purpose: Tests behavior of Override Method feature.
Setup:
#
Test case
Description
1
Invoking Override Methods on class
Create a class and invoke action Tools | Override Methods... (or use shortcut Ctrl+I).
Override and Implement Methods dialog will appear. The dialog contains following controls: list of methods and checkboxes Show superclasses and Interfaces, Show Abstract Methods Only, Generate Super Calls and Copy Javadoc.
RESULT:
Appearance of Override and Implement Methods dialog.
2
Checking Show Superclasses and Interfaces enabled
Enable Show Superclasses and Interfaces checkbox.
Try to disable and enable the Show Abstract Methods Only checkbox.
RESULT:
The tree contains classes and interfaces which your class extends. Interfaces have a different icon than classes. Classes and Interfaces have all public and protected methods or only abstract methods as their children. Depends on Show Abstract Methods Only checkbox'es enabling.
3
Checking Show Superclasses and Interfaces disabled
Disable the Show Superclasses and Interfaces checkbox.
Try to disable and enable the Show Abstract Methods Only checkbox.
RESULT:
The tree contains all public and protected methods or only abstract methods which define super classes or super interfaces of selected class. Depends on Show Abstract Methods Only checkbox'es enabling.
4
Commit dialog
Clicking the OK button should close dialog and insert all methods from selected methods list into Your class. Check it.
RESULT:
Appearance of Override Methods panel
5
Generate Super Calls
Invoke Override and Implementation Methods dialog on some class with 'parents'.
Select a method and enable Generate Super Calls checkbox.
Confirm dialog.
Invoke Override and Implementation Methods dialog on some class with 'parents'.
Select another method and disable Generate Super Calls checkbox.
Confirm dialog.
RESULT:
In the both cases selected method will be append to source of the class. Appended method body is empty if Generate Super Calls checkbox is disabled othervise it contains calling of super class method.
6
Copy Javadoc
Invoke Override and Implementation Methods dialog on some class with 'parents'.
Select a method and enable Copy Javadoc checkbox.
Confirm dialog.
Invoke Override and Implementation Methods dialog on some class with 'parents'.
Select another method and disable Copy Javadoc checkbox.
Confirm dialog.
RESULT:
In the both cases selected method will be appended to source of the class. Appended method body has javadoc from parent's method source if Copy javadoc checkbox is enabled othervise it doesn't have javadoc.
The action should be invoked by editor's popum menu (Fix Imports) or by the keybinding Alt+Shift+F (see Tools|Options|Editing|Editor Settings|Java Editor|Key Bindings).
RESULT:
Fix Import action is by default bind to Alt+Shift+F kebinding and is listed in editor popup menu.
2
Add Import statement
Create a new class.
Write code: Vector v=new Vector(); in a method.
Invoke Fix Import action (Alt+Shif+F).
RESULT:
New import statement import java.util.Vector; is appended at import section of code.
3
Add Imports - choose package
Use a class from the previous case (java.util.Vector is imported).
Add a code List l=new Vector(); into a method body.
Invoke Fix Import action (Alt+Shif+F).
There appears Fix Imports dialog with a table. In the first column of the table you can found list of Class Names which were found in more than one package. The second column contains lists of their fully qualified names.
Select java.util.List to the List and press the OK button.
RESULT:
New import statement import java.util.List; is appended at import section of code.
4
Remove Unused Imports
Use a class from the previous case (java.util.List is imported).
Remove a code line List l=new Vector(); from the source file.
Invoke Fix Import action (Alt+Shif+F).
RESULT:
Import statement import java.util.List; is remove from the import section of code.
Purpose: This suite tests Synchronization between interfaces and it's implelemntation
Setup: Unzip a project from sync.zip and open it in IDE.
#
Test case
Description
1
Simple synchronization test
Add interface ifaces.RootInterface to an existing class, you can do this by 2 ways: by hand or using PropertySheet.
Invoke Tools|Synchronize action.
In appeared confirmation dialog press the Process All button.
RESULT:
Synchronization dialog will appear with all methods from RootInterface. After its confirmation all methods will be added into implementing class.
2
Two interfaces
Let your test java class implements 2 interfaces ifaces.RootInterface and ifaces.OtherInterface.
Invoke Tools|Synchronize action.
RESULT:
Methods from both interfaces(RootInterface and OtherInterface) should be added into implementing class
3
Derived interfaces
Let your test java class implements ifaces.Interface1. Interface1 extends RootInterface.
Invoke Tools|Synchronize action.
RESULT:
Methods from both interfaces(RootInterface and Interface1) should be added into implementing class
4
Two interfaces extends the same ancestor
Let your test java class implements Interface1 and Interface2. Don't forget to add import ifaces.*; statement.
Invoke Tools|Synchronize action.
RESULT:
Methods from both interfaces(Interface1 and Interface2) should be added into implementing class.
5
Interface hierarchy has the same ancestor
Let your test java class implements Interface4. Interface4 extends Inteface1 and Interface2.
Invoke Tools|Synchronize action.
RESULT:
Methods from Interface4, Interface1 and Interface2 should be added into implementing class
6
Mode 'Generate Exception'
Go to Tools | Options | Editing | Java Sources | Source Synchronization. Change Return generation mode to "Generate Exception". Do steps 1.-5.
RESULT:
All generated methods should have throw new UnsupportedOperationException(); in it's body
7
Mode 'return null'
Go to Tools | Options | Editing | Java Sources | Source Synchronization. Change Return generation mode to "return null". Do steps 1.-5.
RESULT:
All generated methods should return 'null' e.g. for int is generated 0, for String is generated null, for boolean is generated false etc.
Auto Synchronization is disabled by default. It can be enabled by options Tools|Options|Editing|Java Sources|Source Synchronization|Synchronization Enabled.
