» tagged pages
» logout

sorted by: recent | see : popular
Content Tagged with unit-testing + Java

DbUnit

DbUnit is a JUnit extension (also usable with Ant) targeted for database-driven projects that, among other things, puts your database into a known state between test runs. DbUnit has the ability to export and import your database data to and from XML datasets.

Hibernate: del.icio.us tag/hibernate

JUnit Factory: Introducing Crap4J

http://crap4j.org/downloads/update/

Eclipse: del.icio.us/tag/eclipse

Web 2.0, REST and BEA Workshop

Bill Roth takes a stab at using the Yahoo geocoding ws with Workshop

XMLbeans: del.icio.us/tag/xmlbeans

Building and Deploying Web Services to Sun Java System Web Server 7.0 With the NetBeans 5.0 IDE

This article describes how to build and test Web services that are based on Java API for XML Web Services (JAX-WS) 2.0 with the built-in capabilities of the NetBeans 5.0 IDE and the plug-in for Sun Java System Web Server 7.0

JAX-WS: del.icio.us/tag/jax-ws

htmlunit

A Java unit testing framework for testing Web based applications.

TestGen4J

TestGen is a collection of open-source tools that automatically generates unit test cases. The first released component of TestGen is TestGen4J. TestGen4J automatically generates JUnit test cases from your own Java class files, or source files. Its primary focus is to exercise boundary value testing of the arguments passed to the method. It uses rules, written in a user-configurable XML file, that defines boundary conditions for the data types. The test code is separated from test data with the help of JTestCase.

Abbot - A Better 'Bot

Abbot is a simple framework for automation and unit and functional testing of Java GUIs, both AWT/Swing and SWT.

Abbot facilitates generating user actions and examining component state and supports recording and playback via user-editable XML (“Costello”).

jWebUnit

jWebUnit is a Java framework that facilitates creation of acceptance tests for Web applications.

Ashcroft: Law Enforcement for Unit Tests

Imposes restrictions that apply only to unit tests and not system tests or integration tests, which are also of great importance to the success of any project. Unit tests, at least one for each class in your codebase, should be clean, decoupled from one another, and run ultra-fast. You should be able to run thousands of unit tests and get your green bar in a few seconds. Achieving that kind of performance takes major discipline on the part of the developer and Ashcroft helps you learn that discipline by failing tests which stray from best practices for unit tests.

Compatible with JUnit and JDK 1.3+