Java Open Source Projects Directory

...dedicated into Java open source projects

  • Increase font size
  • Default font size
  • Decrease font size
Testing Tools

dbmonster

Test data generator for SQL databases.

 

testare

TESTARE is a testing framework that aims to simplify the test development process for distributed enterprise JAVA applications. It tries to achieve this goal by focusing on two main directions:

 * provide straightforward and easy to use "in container" testing capabilities
 * provide native support for test environment management and introspection techniques such as fixtures, global fixtures, probes and guards Its initial focus is on "in ejb container" testing but its extensible architecture makes it very easy to develop support for other execution environments such as SERVLETS, JMS listeners, CORBA ORBs or RMI.

 

testng

TestNG is a testing framework inspired from JUnit and NUnit but introducing some new functionalities that make it more powerful and easier to use, such as: - JSR 175 Annotations (JDK 1.4 is also supported with JavaDoc annotations). - Flexible test configuration. - Default JDK functions for runtime and logging (no dependencies). - Powerful execution model (no more TestSuite). - Supports dependent methods.

 

cactus

Cactus is a simple test framework for unit testing server-side java code (Servlets, EJBs, Tag Libs, Filters, ...). The intent of Cactus is to lower the cost of writing tests for server-side code. It uses JUnit and extends it.

 

jfcunit

jfcUnit enables developers to write test cases for Java Swing based applications. It provides support for: 1. Obtaining handles on Windows/Dialogs opened by the Java code. 2. Locating components within a component hierarchy that occur within the containers found above. 3. Raising events on the found components, e.g. clicking a button, typing text in a TextComponent. 4. Handling testing of components in a thread safe manner. Since version 2.0, jfcUnit provides XML Recording and playback. This allows users to quickly and automatically generate/edit scripts to drive the testing.

 

mockcreator

Given the interface or class, it generates source of Mock object for it.

 

ddsteps

DDSteps is a JUnit extension for building data driven test cases. In a nutshell, DDSteps lets you parameterize your test cases, and run them more than once using different data. Since DDSteps is 100% JUnit compatible, you can run your new data driven test cases just like any old JUnit test case. No IDE plugins or new Ant tasks are required - just add the DDSteps jars to your classpath and you are ready to go! DDSteps uses external test data (in Excel) which is injected into your test case using standard JavaBeans properties. Your test case is run once for each row of data, so adding new tests is just a matter of adding a row of data in Excel. DDSteps integrates best-of-breed toolkits for web and database testing, such as JWebUnit, DbUnit and Spring Framework. By making these toolkits data driven, you can do powerful function testing. Automated end-to-end testing of your website is not only possible - it is easy. Features:

 * Run a JUnit TestCase method many times, each time with different test data.
 * Write tests in Java/JUnit and write data in Excel, using the best tool for each task.
 * Handles massive amounts of test data by keeping data separate from code, thus enabling both to be as compact as possible.
 * Use standard JavaBean getters/setters to fill your testcase with data. You don't have to write any code to pull in data, all that is handled by the DDSteps framework.
 * Tap into the power of property injection which is a complement to dependency injection found in frameworks like Spring. Property injection does not deal with dependencies, it handles simple data, but lots and lots of it.

 

jtr-java-test-runner

JTR (Java Test Runner) is a framework meant for fastening the building of both complex and simple test enviroments. It is based on concepts such as Inversion of Control, and is ready for EJB and JMS testing. The JTR 2.0 framework will give you the chance to code only the testing logic. All the boring middleware-related tasks (connecting to ConnectionFactories, opening connections, sharing connections, opening sessions, handleing exceptions, retrieving administered objects) are carried out by the JTR 2.0 runtime on your behalf according to what you have stated in the jtr.xml configuration file. Thanks to IoC (Inversion Of Control), the JTR 2.0 runtime is able to inject all these resources into your IRunner concrete implementations. This entails that you are not required to actively retrieve the resources you need: you declaratively tell the JTR 2.0 framework you are going to need them at runtime, and Inversion Of Control will do the work. The thing same happens with EJBs: all the low-level details are always handled by the JTR framework to let you work only on the pure logic of your tests.

 


Page 3 of 7