JunitScenario is an automation framework on top of JUnit
to perform functional tests and stressing tests. JUnitScenario is a
tool to simulate real life usage of applications. It allows you to
describe scenarios that are composed of unit tests calls and simulate
several users following those scenarios.
February 16, 2005
With this junit-extension you can create some tests or just their 'skeleton', 'mark them as 'prepared' by throwing an Exception, and develop your whole software continuously while concentrating on the main test!
This library helps you to make your Xtreme programming process more effective or just helps you doing any refactorings! With an automatic report about missing / not finished test cases, any programmer has a better overview about his work!
November 15, 2003
Haste (High-level Automated System Test Environment) represents an approach to system testing that is philosophically consistent with standard XP unit testing practices. Test code runs in the same address space as the application under test, allowing for ready examination of application state. The fundamental Haste abstractions of Story, Step, and StoryBook provide a framework to implement system tests. Utility classes simplify test development. In addition to acting as XP acceptance tests, Haste tests aid source maintenance and extension, and can play an important role in a release process.
February 26, 2003
Jameleon is an acceptance-level automated testing tool that separates applications into features and allows those features to be tied together independently, creating test-cases. These test-cases can then be data-driven and executed against different environments. Even though it would be possible to write unit tests using Jameleon, Jameleon was designed with integration and acceptance-level testing in mind.
June 27, 2003
GroboUtils aims to expand the testing possibilities of Java. It contains many sub-projects which experiment with one aspect of testing through Java.
December 19, 2002
PicoContainer is very simple container for very simple components. It honors the Inversion of control pattern (IoC) in a way we calling type 3 IoC. This is particularly good for unit testing. In-container testing being one of the most avoided forms of unit testing.� This is where other container designs and specifications fail.
June 15, 2003
Automatic Regression Testing
There is a lack of automation tools and statistical publishing of results for JUnit tests, XTest provides this automation and publishing around your collection of JUnit tests. XTest is a testing framework used for testing Java products through JUnit, HttpUnit (and hopefully soon Cactus) type tests, and publishing the results into html pages. It integrates testing from multiple platforms, products, product versions, and test types, to provide upto date comprehensive statistical information about the status of your java code.
October 21, 2003
JUnit JNDI DataSource helper package
The JUnit JNDI DataSource helper package can be used to Simulate JNDI lookups for Database Connections.
December 20, 2002
SQLUnit is a regression and unit testing harness for testing database stored procedures. The test suite is written as an XML file. The SQLUnit harness itself is written in Java and uses the JUnit unit testing framework to convert the XML test specifications to JDBC calls and compare the results generated from the calls with the specified results.
May 06, 2003
SUT: XML Schema Unit Test
W3C Schema can quickly become complex and difficult to determine if they are validating the correct vocabulary. The addition of embedded Schematron schema only makes this problem worse. Schema Unit Test (SUT) introduces a framework for testing XML Schema.
March 23, 2003
Log4Unit is a JUnit extension combining JUnit with Log4J. The intention is to create test protocols for JUnit. JUnit is asymmetrical in the sense that it focusses on the documentation of test failures and errors. Successful execution of a test case is not further documented. In order to obtain a test protocol that documents the initial settings, the test case execution and its results, a logging component is required. Log4J as the current de facto standard is selected for this extension.
March 21, 2002
Artima SuiteRunner Project
Artima SuiteRunner is a free open source testing toolkit for Java released under the Open Software License. You can use this tool with JUnit to run existing JUnit test suites, or standalone to create unit and conformance tests for Java APIs. The three main advantages Artima SuiteRunner offers to JUnit users are reporters, runpaths, and recipe files. Existing JUnit users can use SuiteRunner to run their JUnit tests, which allows them to gain the benefits of reporters, runpaths, and recipe files while continuing to use their JUnit test cases.
January 27, 2003
RV Message Testing Framework
The Message Testing Library is an extension to JUnit that allows for server, integration, and load testing of TIBCO Rendezvous based solutions.
January 21, 2003
Convert JUnit assert to assertTrue
Starting from jdk 1.4 the new java keyword assert collides with the junit assert. assertTrue was introduced in junit 3.7 to solve this problem. The following bash script can be used to replace all assert with assertTrue.
January 01, 2001
JUnit-addons is a Collection of classes to facilitate the use of JUnit.
August 18, 2002
Avignon is an acceptance testing framework written by Narti Kitiyakara for the Cyndrus ADS project. For programming teams that use the Extreme Programming (XP) methodology, Avignon lets customers express acceptance tests in a non-ambiguous manner before development starts.
August 01, 2002
Lisa provides; regression testing for Web sites and Web services, functional testing, load testing (with purchase) and, Java-based extensibility.
June 20, 2002
GSBase Testing classes
A collection of classes that are helpful when writing JUnit test cases; RecursiveTestSuite, OrderedTestSuite, EventCatcher, and EqualsTester.
January 01, 2002
Hansel is an extension to JUnit that adds code coverage testing to the testing framework. Currently only basic block coverage is supported.
Much of the source code is taken from Gretel a "Residual Test Coverage Monitoring"-Tool developed at the University of Oregon.
May 22, 2002
JTestCase helps you in seperating test data from test code. In another word, JTestCase enables
unit tests to be "data-centric".
April 10, 2002
JFunc: JUnit Functional Testing Extension
JFunc is an extension to the JUnit testing framework to make it easier for use with functional tests. Functional testing (also called integration testing) significantly differs from unit testing in a number of respects. Part of this project is dedicated towards putting together code to address these differences; the other part of this project is putting together methodologies for functional testing.
Shane Celis ,
April 23, 2002
a TestRunner subclass that will output results into documents in a Domino database - this makes it a bit easier to work with JUnit
when writing Java code for Domino, as you can run a Domino agent to run the tests and the results will appear in a view within the database.
March 28, 2002
JUnit and Enhydra
This article introduce the use of Java based Unit Test framework JUnit and how to apply JUnit to Enhydra.
November 13, 2001
Why would I want to use XPath Explorer? Maybe you're trying to write an XSL stylesheet and you're tearing your hair out because a complicated XPath matching expression doesn't match what you think it should, and you need some debugging help. Maybe you're using HTTPUnit to unit test your Web site, and you're sick of using the W3C DOM classes to painstakingly walk down your DOM tree. You can use XPath to jump immediately to the value you're looking for and assert that it's present. Using Jaxen, that's as easy as...
March 21, 2002
XMLUnit extends JUnit to simplify unit testing of XML. It compares a control XML document to a test document or the result of a transformation, validates documents against a DTD, and (from v0.5) compares the results of XPath expressions.
March 19, 2001
The dbUnit database testing framework is a JUnit extension which sets up your database in a known state before executing your tests. This framework uses xml datasets (collection of data tables) and performs database operations before and after each test. The dbUnit framework supports both the clean insert and the refresh strategies.
February 28, 2002
JUnit for J2ME
December 23, 2001
How Good are your JUnit Tests? NoUnit measures your Junit tests in your project using Java, XML and XSLT. NoUnit gives a picture of your code , like a graph gives you a picture of a set of figures, to allow you to see what is *really* going on.
December 23, 2001
JUnitX and XPTest
JUnitX provides access to private and protected classes, methods and variables between different packages for testing purposes. It works as module on top of the lastest JUnit version. XPTest integrates JUnit and JUnitX into the UML modelling tool Together. Using the Together patterns and code generators of XPTest, it is possible to create and maintain tests automatically.
November 03, 2001
Using JUnit with TIBCO
Write testcases for your TIBCO Active Enterprise application.
October 26, 2001
Daedalos JUnit Extensions
The Daedalos JUnitExtensions make it possible to define test resources as known from the Smalltalk SUnit. Unit tests are speeded up by using test resources, because time-consuming initializations are only done once and remain active over a series of tests. As an example, a database connection is opened before executing the first unit test and can be accessed during the whole testing circle. It isn't necessary to re-open the database connection before an unit test is executed.
July 20, 2001
JUnitPP is a freely available Java unit test framework that includes a test data repository, command-line arguments, and a TestRunner class that supports a built-in repetition counter and multithreading at the command line.
July 04, 2001
Building Suites of Test Data with XML: Data-Centric Testing: Advantage of Separating Test Data from Test Code.
April 18, 2001
Regression testing is a necessary, yet expensive, software maintenance activity. Regression testing is commonly used to determine whether the modifications made to a software system have introduced new faults. Many different techniques have been proposed in an attempt to make the regression testing process more cost-effective and practical. We are involved with the development of the conceptual foundation, design, and implementation of Joshua. Joshua is a tool that facilitiates the distributed execution of regression test suites. Our regression testing tool is an extension of the JUnit (3.2) testing framework that relies upon the Jini network technology and the JavaSpaces object repository to perform test case distribution.
March 22, 2001
A collection of JUnit test decorators to test the performance and scalability of functionality contained within existing JUnit tests.
March 12, 2001
JDepend traverses a set of Java class and source file directories and generates design quality metrics for each Java package. JDepend allows you to automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability to effectively manage and control package dependencies. JDepend can be automated so metrics never go stale or require visual inspection. Tolerances for certain metrics, for example the distance from the main sequence (D), can be codified in a JUnit test case that automatically checks the metrics for conformance to a desired result and provides immediate visual feedback. As the software evolves through refactorings, the design quality test cases can be run as a sanity check to insure that the design hasn't formed too many undesirable dependencies.
February 14, 2001
Finds code that is not covered by tests. JesTer makes some change to your code, runs your tests, and if the tests pass JesTer displays a message saying what it changed. JesTer is different than code coverage tools, because it can find code that is executed by the running of tests but not actually tested. However, JesTer is not meant as a replacement for code coverage tools, merely as a complementary approach.
February 14, 2001