Search Results for "junit"

This project provides a meaningful way to increase code coverage of your jUnit and TestNG tests. Unit testing Java Beans can be a tedious task. The goal of this project is to provide an automated way to unit test the getters and setters of a class.

A group of Java-based testing tools and JUnit extensions aimed at increasing quality awareness and ease of introduction of testing tools into the development cycle. Examples are Automated documentation, class hierarchy unit testing, and code coverage.

...This is tedious and error-prone, and keeps developers away from writing more meaningful unit tests. Easy Coverage is extensible and highly configurable. It can work as a standalone product, or be used with JUnit, which is highly recommended. Support for TestNG is planned. If you want to get started, you should go to the wiki and the quick start.

The Automatic JUnit Creation Tool analyzes java classes to map all possible test branches. The tool then guides users through the generation of a JUnit test.

An eclipse plugin for code coverage visualization of JUnit Tests. Especially useful for test-first development. Supported coverages include block coverage and all-uses coverage (Data Flow Analysis).

ZK Unit extends JUnit to test your ZK project: ZUL pages, composers, event handlers, constraints and more. Use ZKUnit for test driven development, to achieve code coverage and integration with a continous build system.

Unzip buildtemplate and you will have a project set up with ant/junit/verifydesign/code coverage all out of the box. It is a great way to get started and then add to the build.xml as you go. netbuildtemplate is for .net and has nant/nunit/NCover, etc.

Hansel is an extension to JUnit implementing code coverage tests.

EL4Ant is a light and efficient build system based on Apache Ant. A project is described in XML as modules with transitive dependencies. Features are provided thanks to plugins: Java execution, JUnit reports, EMMA code coverage, Eclipse integration...

A toolbox for testing SQL. Currently, SQL Spelunk includes code coverage analysis and calling stored procedures in a rolled-back transaction from SQL and JUnit.

Java Web Application Stack built on top of Wicket, Spring, Hibernate/Ibatis, Jetty, HSQLDB, Junit, functional testing (Selenium), code coverage(Cobertura), DB Migration and CI. Its intent is to provide a rapid method for creating java web new projects

Measure how directly your classes are tested by JUnit. Unlike traditional code coverage tools, PEA considers and measures whether the code covered ran as a direct call from a test, or indirectly via chained calls.

JUnitMetrics is a tool that enables to measure basic JUnit and Cactus tests metrics (like number of tests, assertions, number of executed assertions). It is great, complementary solution to code coverage tools and mutation testers.