Create your own tests for Java/EJB code
- By Adam Wallace
scripted Java GUI testing framework that supports recording and playback of
semantic user events, and component state evaluation for both unit and
you to record scripts using Java GUI components and then play them back in JUnit
or alone in Pounder. It is licensed under the GNU Library General Public
Jemmy Module <>http://jemmy.netbeans.org/>
a Java library that is used to create automated tests for Java GUI apps. It
contains methods to reproduce all user actions that can be performed on Swing
components (button pushing, text typing, tree node expanding). JemmyTest is a
program written in Java that uses the Jemmy API to test apps. Jemmy is a
NetBeans-independent module that can be used separately as well with the
extension to the JUnit framework that enables users to execute unit tests
against code that presents a Swing-based interface.
Server Test Case
An extension to JUnit for running test cases inside an EJB
server. It makes server tests as easy to write and run as other tests.
EJB Monitor for WebLogic 6.0/6.1 EJB/J2EE
write your tests using JUnit or Cactus and add the test class to EJB Monitor.
You can monitor your test classes, EJBs and pool connections.
Epicentric JUnit JSP test harness <>http://www.junit.org>
Web-based JUnit test harness that provides an intuitive, point-and-click
interface for running unit tests and viewing results. It allows you to upload
and run test classes against remote servers for platform testing/debugging,
provides an effective framework to verify Java code running within a particular
JSP framework, and commercial load-testing software can be used to drive the
Web-based interface to conduct Java or JSP framework load testing.
Simple classes to help test JSPs <>http://www.dallaway.com/jsptest/>
Test is a collection of Java classes to help you test JSPs automatically.
is a simple test framework for unit testing server-side Java code (Servlets,
EJBs, Tag Libs, Filters). It is an extension of the JUnit testing framework.
from this site is TestRunner, which outputs HTML and a servlet that can be used
as an entry point. Building your test harness as a standard J2EE Web app means
your tests are packaged conveniently into a .war file that can be moved between
servers; you can leave the .war file in the main .ear file and simply avoid
enabling the test Web app on the production server; test classes will be
dynamically reloaded by the app server (assuming your server supports this);
test cases look just like your production code; and you can use the same beans
(or whatever) you use as a facade for your EJBs.
See the related stories, '' Testing key to component
quality,'' '.NET and
Java: No real integration yet,' 'Testing Web services: Even more
complex' 'Representative testing
tools' and 'Extending the testing
Courtesy of Adam Wallace, Flashline Inc.