Open Source Java Software Testing Tools

The Software Testing Automation Framework (STAF) is a framework designed to improve the level of reuse and automation in test cases and test environments. The goal of STAF is to provide a complete end-to-end automation solution for testers.

This profiler (JRE 1.5.0 only) uses JVMTI and native bytecode instrumentation for the analysis of the heap, reachable objects, execution time, garbage collection efficiency, code coverage and thread contention. No preparation steps required in build.

The SpeedTest program is used to test the speed of Java code on various computer platforms. It runs tests such as 500,00 sin & cos calculations, allocate an array of 5,000 doubles 50,000 times, and allocate an array of 50,000 points 20 times.

This is a collection of Eclipse plug-ins that help you work with .NET. If you used tools like Emonic, this is something that will be helpful. Current functional tools include NUnit and NAnt support. Both tools work like their Java equivalents.

Open Source Application Server Appliance based on Open Source GlassFish

BugUnit extends JUnit with the concept of a 'bug'. Multiple tests test one bug, if one test fails the bug is open. Methods like assertEquals("PRJ-123",i,10) will flag bug PRJ-123 as open or closed in Jira and a bug-centric HTML summary.

CouchUnit is a Java Testing Framework, similar to DBUnit, that eases the construction and execution of Integration Tests against CouchDB Datasources.

A selenium framework to do automation testing without any prior selenium knowledge and without any programming knowledge.

FastAOP is an very high performant AOP (Aspect Oriented Programming) framework for java. The framework was initially developped to support performance profiling and monitoring for large J2EE applications with nearly no runntime overhad. Announcement: jp-mobile and fastAOP will go mobile, please visit jp-mobile (GWT based) website at: http://code.google.com/p/jp-mobile/

Modern software systems and application are commonly written in multiple languages, include scripting engines, and are frequently build on multiple specialized frameworks and middleware for a considerable diversity of runtime environments. The latest influencing update in development paradigm is the application of multicore processors. This projects is aimed to unify the required trace and logging output and integrate into debugging environments. The target is to provide general development, test, and production support of software environments based on multiple programming languages for distributed multicore environments.

BeanClipse is a NetBeans plugin for Eclipse: NetBeans runs embedded within the Eclipse platform as a plugin offering the best of both worlds to Java developers. May be just a joke ;-) .... Check also it's twin at : http://sf.net/projects/netclipse

CUBRID QA project contains a test-automation tool and many kinds of test cases for CUBRID database.

Automation of Unit and System Tests. Tests can be implemented in any language and on many platforms. The flexible approach enables the inclusion of many types of tests, such as memory leak checks (using valgrind), coding rule checks, complexity checks, etc. Tests are run by a simple call to hwut in a base directory of a project. In particular for C, HWUT supports make file generation using 'sos' and 'sols' modes. Remote control-able function stubs may be generated using the 'stub' mode. Test cases can be generated using the 'gen' mode, and state machine walkers by the 'sm_walker' mode. Over the last decade HWUT has matured towards a full fledged unit test tool for a wide variety of applications.

In order to assure software performance, software needs to be tested accordingly as early as possible - only weaknesses diagnosed early can be assessed quickly and cheaply. ContiPerf enables performance testing already in early development phases and in an easy-to-learn manner: A developer writes a performance test in form of a JUnit 4 test case and adds performance test execution settings as well as performance requirements in form of Java annotations. When JUnit is invoked by an IDE, build script or build server, ContiPerf activates, performs the tests and creates an HTML report. The report provides a detailed overview of execution, requirements and measurements, even providing a latency distribution chart. A large feature set for execution settings and performance requirements is available, e.g. Ramp up, warm up, individual pause timing, concurrent exection of test groups and more.

The software program (SarBox) parses and analyzes SAR data in charts or text formats. SAR is cumulative activity counters in the operating system. It is the most comprehensive command which helps to monitor performance of various Linux / Solaris subsystems (CPU, Memory, I/O, Disk, Network, etc) all in same log. This makes it difficult to analyze since every counter data is dumped into the log file. SarBox helps to analyze this log file and present data in graphical charts or text format. To collect sar statistics from an environment, use below syntax [user@host ~]# sar -A 30 2 > sar_linux.log “30 2” reports for every 30 seconds and total of 2 times, written in sar_linux.log.

Support automatic exposure of mock/proxy pairs into a Spring container.

Test Drive is an automation tool. The application is specifically aimed at testing network based services that make use of popular protocols i.e HTTP, SOAP, ICAP, DNS etc.

Tired of bogging down your machine to RUN all the TESTS, having to WAIT for the CruiseControl build to be green, or causing other developers HEARTACHE by skipping these steps when checking in your changes to source control? The Patch Process Is for YOU!

This open source software benchmarks the queries per second of an Apache Lucene index. It is an Java implementation and uses MultiFieldQueryParser to form a query.

An executable Jar file contains both a Swing-based editor with syntax-highlighting, online help, example generator etc. for the "httest" tool (https://sourceforge.net/projects/htt/), as well as a Java API wrapper for writing JUnit tests with "httest".