This is one of those plug-in which a developer would love to have in the development environment, the main purpose of this plug-in is report the time taken to execute a JUnit.
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
Written by Ravi Nallakukkala on April 16th, 2007 with no comments.
Read more articles on Tools.
A tool for creating JUnit tests (class/ methods).
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
Written by Ravi Nallakukkala on April 16th, 2007 with no comments.
Read more articles on Tools.
Found a good discussion on IBM site; but remember this is a discussion in 2003 things could have changed by now
Written by Ravi Nallakukkala on April 16th, 2007 with no comments.
Read more articles on Uncategorized.
This is a plugin meant for running all JUnits as a single test suite.
Highlights
- 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.
Written by Ravi Nallakukkala on April 16th, 2007 with no comments.
Read more articles on Tools.
Continuing the quest for a JUnit generator tool, my next stop was with JUnit Generator – IntelliJ Plugin. Lets look at features and the fitments of this tool towards my requirement (Junit Generation for a given source code).
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
Written by Ravi Nallakukkala on April 16th, 2007 with no comments.
Read more articles on Tools.
I started a searching for a free tool (which hopefully) will generated some JUnit test code for a given source code. In process of this search, as a first start point I started evaluating the plug-ins which are available for IntelliJ; JUnit 4 Synchronizer is my first stop in the evaluation process.
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
Written by Ravi Nallakukkala on April 16th, 2007 with no comments.
Read more articles on Tools.