Highlights (release 0.4)

• Reports the time taken for the execution of each test method, typically the results are displayed in as shown below.

Usage

• Upon running a JUnit test class, this plug-in gets invoked automatically.

Favorable

• Great reports in development environment, no need for any extra profiling.

Unfavorable

• This plug-in doesn’t integrate with Fireworks plug-in (through which you can run a test suite)

For more information about this tool, IntelliJ plug-in repository here and user documentation here

Highlights (based on release 0.303)

• Extremely easy to use, very well documented.
• You can create your own location patterns for the Test class to be created.

Usage

• On a class or method press Ctrl-T (in Ariadna) Ctrl-Shift-T (in Aurora) to go to the test class or test method
• On a test class or test method press Ctrl-T/Ctrl-Shift-T to go back to the tested class or tested method
• If the test class or test method is missing it will be automatically created.

Favorable

• Easy of use and integrates well with IntelliJ
• You have more control on the location of the created test classes.
• Very good documentation.
• Toggle between the code and test using CTRL + SHIFT + T
• This plug-in along with fireworks plug-in should be good fit.

Unfavorable

• Not an Intelligent to analysis the code and write some test cases.

For more information on this tool here and User guide available here

• Runs with JUnit 3.8 and 4.
• Helps in Run all the JUnits together (as a single test suite) based on a regular expression (e.g, *test).

Usage

• Goto fireworks tab and select run (ALT + SHIFT +K).

Favorable

• Helps to run all the JUnit together and Integrates with IntelliJ

Unfavorable
NA

For more information on this tool here.

Highlights (based on 1.1.7 release)

• Generates JUnit test classes/methods for all the public source methods .
• The generated JUnit code is not complaint with JUnit 4.
• Easy of Installation/ usage.

Usage

• Open the file for which you need to write the JUnit test class, select Alt+Insert you will see “JUnit Test” menu in the list.

Favorable

• Auto generates the skeleton code for JUnit test class.
• Integrates with IntelliJ

Unfavorable

• Only the Skeleton code is generated.
• If the JUnit already existing, For an Existing JUnit IntelliJ (6.0.5 build #6180) throws an Internal error instead of showing the differences in the current JUnit code to generated code as promised by the tool

For more information about this tool, go from here

Highlights (based on release 0.1.1)

• Generates Skeleton JUnit Code.
• Generates JUnit 4 test classes/methods for source methods annotated with the @Testable annotation.

Usage

• From IntelliJ IDE, Tools –> RunSynchronize JUnit Tests, this creates a @Testable annotation
• All the desired source methods needs to be Annotate with @Testable annotation.
• Run Synchronize JUnit Tests to create test methods.
• Repeat steps 2 and 3 as often as desired to create new unit tests

Favorable

• Auto generates the skeleton code for JUnit test class.
• Integrates with IntelliJ

Unfavorable

• Source code needs to have test Annotations in the source code. In other words, Source code has dependency on test code (as @Testable annotation is available in ‘test’ folder).
• Only the Skeleton code is generate

For more information about the plugin, go here

This is different from Bean utils, which copies the data recursively for the object which has the same property names. Bean-Utils has a restriction for working with complex data types.

Dozer tool can be found here

here’s some of the key advantages found on Dozer

• Can define the mapping / exlude mapping in a configuration mapping file.
• Support for Spring (tested Dozer 3.0/ 3.1 with Spring 2.0).

Recommanded Usage Scenario:

• Highly recommanded for the scenarios, where the usage of design patterns for Data Transfer Object (Dto) and Business Objects (Bo).
• For scenario of Data transfer from UI form elements to Data transfer objects (Dto).

Disadvantages for Dozer

• I used this tool under Java 5/ Spring 2.0. Dozer was instantiated using Spring. our architecture was like, all the business Objects (Bo) were placed in one project. Had a facade (facade has Dto) for a set of functionalitie. Now the problem was the definition of spring configuration for the dozer, as Dto and Bo were present in various projects, so this created a need for the definition spring configuration definition on a top level project than at leaf level.